Update schema

[mitchdenny]

Description

Updating the schema to aspire-9.0. Just a rename of everything.

Fixes #6581

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No
• Does the change require an update in our Aspire docs?
  • Yes
    • Is this introducing a breaking change?
      • Yes
        • Link to aspire-docs issue (please use this breaking-change template):
      • No
        • Link to aspire-docs issue (please use this doc-idea template):
  • No

[danmoseley]

OK, schema is now fixed so that it passes the strict validation at schemastore on both 8.0 and latest manifests.

[danmoseley]

@davidfowl easy one to signoff & merge

[davidfowl]

@danmoseley @captainsafia made schema changes in 9.1. So, we'll need to do this again.

[captainsafia]

@danmoseley @captainsafia made schema changes in 9.1. So, we'll need to do this again.

I assume you mean just a rename? I've already updated the schema with the changes needed for existing resources work.

[danmoseley]

Yes, if you mean 4e1a0f2 then it's already in here and what I uploaded