Update Current to current for securityContext schema

[Gijsreyn]

PR Summary

This pull request is a minor change to reflect all schemas to current for the securityContext canonical property.

PR Context

Fix #1055

[michaeltlombardi]

Thanks for this contribution!

It looks like you went through to fix the composed schemas directly.

What we actually want to do is:

1. Update the following line in schemas/src/config/document.metadata.yaml:

   DSC/schemas/src/config/document.metadata.yaml

   Line 35 in 728b529

   default: Current

2. Regenerate the schemas for only the v3* version folders.

We don't want to modify the schemas for 2024/04, because those map to before we canonicalized the casing for enums.

[Gijsreyn]

Hi Mikey,

Thanks for checking the pull request. I was already afraid that I was doing something wrong. I had tried running the build.ps1 script in the schemas directory, but couldn't get it to work. I guess I had the powershell-yaml module installed, rather than the yayaml. Anyway, the steps that I did now:

1. Change what you suggested in step 1.
2. Run the build.ps1 script for each v3.* version by modifying the schemas.config.yaml file.

Hope that these are the steps.

[michaeltlombardi]

It looks like a lot of files got inadvertent updates because of the complexity for regenerating schemas. I'm going to see if I can tackle the build to filter these values based on the target version (e.g. v3.0.0 shouldn't consider later versions at all, v3.0 shouldn't consider 3.1 or later, v3 shouldn't consider 4.0.0 or later).

For now, I consider my initial recommendation to be erroneous - instead of updating source and regenerating, we should just update source and the generated schemas. I'll have to tackle the build separately. I'm going to take over this PR to get it into a mergeable state, since it's my fault that the changes ended up like this.

[Gijsreyn]

Solid copy, sir!