[GPO] Fix the admx file by removing obsolete using

[htcfreek]

Summary of the Pull Request

There was an obsolete using that prevented users from import into Intune management.

PR Checklist

• Closes: Can't import ADMX on Intune #21702
• Communication: I've discussed this with core contributors already. If work hasn't been agreed, this work might be rejected
• Tests: Added/updated and all pass
• Localization: All end user facing strings can be localized
• Dev docs: Added/updated
• New binaries: Added on the required places
  • JSON for signing for new binaries
  • WXS for installer for new binaries and localization folder
  • YML for CI pipeline for new test projects
  • YML for signed pipeline
• Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx

Detailed Description of the Pull Request / Additional comments

In addition to the fix this PR adds a version information file. This file helps users to identify the downloaded admx later.

Validation Steps Performed

nothing

[htcfreek]

@jaimecbernardo
Are you okay with the new version file?
Do we need some additional changes to add the version file to the release download asset?

[jaimecbernardo]

Sure, I'm OK with the version file. It does feel somewhat extra. There's also references to the revision in the .admx and .adml for that.
No need to up the revision here since we're only removing the namespace, but that'll be needed for the future.
What about just adding it in comment to the .admx instead of adding a new file, since it already contains the revision? <!-- PowerToys 0.64.0 -->

[htcfreek]

Comment sounds good too. The revision 1 was only for the "using" fix.

[jaimecbernardo]

Hi @htcfreek , added the PowerToys version next to the needed revision. LGTY?

[jaimecbernardo]

LGTM! Thank you for the contribution! 😉

[jaimecbernardo]

Merging so we can include in the hotfix. Other formats may be done for 0.65 if needed.