Update Aspire feature collection location

[Mitch Denny (mitchdenny)]

What type of PR is this?

• Add a new dev container collection
• Update to an existing dev container collection
• Documentation/spec update
• Other containers.dev site update (UX, layout, etc)

Related Issues

None.

Description

Update the existing .NET Aspire collection to its current Microsoft repository and registry namespace:

• Repository: https://github.com/microsoft/aspire-devcontainer-feature
• Issue contact: https://github.com/microsoft/aspire/issues
• Maintainer: Aspire team
• Collection OCI reference: ghcr.io/microsoft/aspire-devcontainer-feature

Publication verified after microsoft/aspire-devcontainer-feature#30 merged:

• The release workflow for merge commit c745d4f0ff976ec73ce7bd0049fd92a31bbf9d92 completed successfully, including metadata validation, amd64/arm64 test jobs, and publication.
• Anonymous GHCR requests successfully retrieved the collection-root latest manifest and its devcontainer-collection.json layer, which lists the aspire Feature at version 3.1.0.
• The individual Feature artifact is publicly downloadable at ghcr.io/microsoft/aspire-devcontainer-feature/aspire:3.1.0. Tags 3.1, 3, and latest resolve to the same manifest. Downloaded artifact layer SHA-256 digests were verified.
• Both collection and packaged Feature metadata confirm version 3.1.0, useDailyBuilds defaulting to false, and only microsoft-aspire.aspire-vscode in the VS Code extension list.

The index retains the collection-root reference, not the individual Feature path. The repository is public and active, and the maintainer contact targets the active Aspire repository with issues enabled. This updates the existing collection in place without adding a duplicate entry.

Validation: yamllint --strict -c .github/lint-config.yaml _data/collection-index.yml passed; git diff --check passed.

Collection checklist

If your PR contributes a new collection, please utilize this checklist:

• Collection name
• Maintainer name
• Maintainer contact link (i.e. link to a GitHub repo, email)
• Repository URL
• OCI Reference (must be the collection root, e.g. ghcr.io/<owner>/<repo> — one entry per repository, not one per Feature; do not include http:// or https://)
• I acknowledge that this collection provides new functionality, distinct from the existing collections part of this index.

The final new-functionality acknowledgement is not applicable: this PR relocates an existing indexed collection rather than contributing a new collection.

[Mitch Denny (mitchdenny)]

Thanks for merging Christof Marti (@chrmarti)