Add encoded parameters documentation to manifest format

[Copilot]

Syncs manifest-format.mdx with changes from dotnet/docs-aspire#5317.

Changes

• Encoded parameter resources: Added documentation for annotated.string type with filter support
  • Projection naming: {parameter}-{format}-encoded
  • Example: URI-encoded password projection with filter: "uri"
  • Original parameters preserved for secret metadata

Note: Both environment variable formats are present in the documentation:

• Original format: APISERVICE_HTTP / APISERVICE_HTTPS
• Protocol-scoped format: services__apiservice__http__0 / services__apiservice__https__0

Example

"redis-password-uri-encoded": {
  "type": "annotated.string",
  "value": "{redis-password.value}",
  "filter": "uri"
}

Original prompt

Please create a PR to update the manifest-format.mdx based on this PR: dotnet/docs-aspire#5317

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[IEvangelist]

Please address my feedback

[Copilot]

Please address my feedback

Addressed all feedback in commit b5f0344. Reverted socials.config.ts and kept the APISERVICE_HTTP/APISERVICE_HTTPS variables while adding only the new encoded parameters documentation.

[Copilot]

Pull request overview

This PR adds documentation for encoded parameter resources in the Aspire deployment manifest format, syncing with changes from dotnet/docs-aspire#5317. The documentation explains how filtered/encoded parameter values are represented in the manifest using the new annotated.string resource type.

Key changes:

• Documents the annotated.string resource type for representing filtered parameter projections
• Explains the naming convention for encoded parameters ({parameter}-{format}-encoded)
• Provides an example of URI-encoded password projection

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The phrase "Names are deduplicated if multiple projections share the same base" is ambiguous and could confuse readers. It's unclear what happens during deduplication (e.g., are suffixes added like -1, -2?) and when this scenario would occur. Consider either removing this sentence if it's an edge case that rarely happens, or providing a concrete example showing how names are deduplicated.

Suggested change

	- The resource name is derived from the parameter name and format (`{parameter}-{format}-encoded`). Names are deduplicated if multiple projections share the same base.
	- The resource name is derived from the parameter name and format (`{parameter}-{format}-encoded`).

[Copilot]

Two clarity issues in this sentence:

1. The term "projection" is introduced without explanation. Readers may not understand what "filtered projection" means in this context. Consider using simpler terminology like "filtered version" or "encoded representation", or add a brief explanation.
2. The phrase "When a parameter is using a filter" could be clearer. Consider rephrasing to "When a filter is applied to a parameter" to more accurately describe the relationship.