Update the $schema URIs for manifests to 2023/10

[michaeltlombardi]

Summary of the new feature / enhancement

In the most recent set of unreleased changes, we have backwards-incompatible updates to the schemas. We have so far been updating the schemas in place during early development, but we will need to update the schemas in a more graceful way eventually.

We should practice doing so now while the impact is minimal to figure out a workflow and practice that suits our needs so that when many users and integrating developers are depending on the schemas, they can do so with confidence.

Proposed technical implementation details (optional)

We should update the schema constants for configuration documents and resource manifests from string constants to enum values:

DSC/dsc_lib/src/configure/config_doc.rs

Line 81 in 94c0f63

const SCHEMA: &str = "https://raw.githubusercontent.com/PowerShell/DSC/main/schemas/2023/08/config/document.json";

DSC/dsc_lib/src/dscresources/resource_manifest.rs

Line 191 in 94c0f63

const MANIFEST_SCHEMA_VERSION: &str = "https://raw.githubusercontent.com/PowerShell/DSC/main/schemas/2023/08/bundled/resource/manifest.json";

This is pseudocode, since I'm not quite familiar with Rust yet, but something like:

#[derive(Debug, Clone, PartialEq, Deserialize, Serialize, JsonSchema)]
pub enum SchemaUri {
    #[serde(rename = "https://raw.githubusercontent.com/PowerShell/DSC/main/schemas/2023/10/config/document.json")]
    Version2023_10 = "https://raw.githubusercontent.com/PowerShell/DSC/main/schemas/2023/10/config/document.json",
    #[serde(rename = "https://raw.githubusercontent.com/PowerShell/DSC/main/schemas/2023/08/config/document.json")]
    Version2023_08 = "https://raw.githubusercontent.com/PowerShell/DSC/main/schemas/2023/08/config/document.json",
}

To allow users to specify a valid schema. We should begin considering whether/how to address schema changes between versions, but I don't think we need any specific handling at this time.