Update CLI confirmation prompts to use [Y/n] convention

[Copilot]

CLI confirmation prompts showed default values as [y/n] (y): — a non-standard format. The convention is to capitalize the default choice: [Y/n].

Before: Perform updates? [y/n] (y):
After: Perform updates? [Y/n]:

Changes

• ConsoleInteractionService.ConfirmAsync: Replace IAnsiConsole.ConfirmAsync (which renders Spectre's [y/n] (y) format) with a ConfirmationPrompt that has ShowChoices = false and ShowDefaultValue = false, and manually prepend [Y/n] or [y/N] to the prompt text based on defaultValue.

var yesChoice = defaultValue ? "Y" : "y";
var noChoice = defaultValue ? "n" : "N";
var fullPromptText = $"{promptText} [{yesChoice}/{noChoice}]";

var prompt = new ConfirmationPrompt(fullPromptText)
{
    ShowChoices = false,
    ShowDefaultValue = false,
};

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
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
  • No
• Does the change require an update in our Aspire docs?
  • Yes
  • No

---

⌨️ Start Copilot coding agent tasks without leaving your editor — available in VS Code, Visual Studio, JetBrains IDEs and Eclipse.

[Copilot]

Pull request overview

Updates Aspire CLI confirmation prompts to follow the common convention of capitalizing the default choice ([Y/n] or [y/N]) instead of Spectre.Console’s default [y/n] (y) rendering.

Changes:

• Replaces IAnsiConsole.ConfirmAsync(...) with a manually-configured ConfirmationPrompt.
• Hides Spectre’s built-in choices/default display and prepends a custom [Y/n] or [y/N] suffix to the prompt text.

[Copilot]

fullPromptText embeds [Y/n] using single brackets, but Spectre.Console treats [...] as markup tags. This will render incorrectly and can throw InvalidMarkupException because there’s no closing tag. Escape the choice suffix (e.g., use doubled brackets [[...]] or otherwise ensure the brackets are treated as literal text).

Suggested change

	var fullPromptText = $"{promptText} [{yesChoice}/{noChoice}]";
	var fullPromptText = $"{promptText} [[{yesChoice}/{noChoice}]]";

[Copilot]

defaultValue is now only used to choose the casing for Y/n, but it is no longer applied to the prompt behavior. To preserve the method contract, set the ConfirmationPrompt default (e.g., prompt.DefaultValue = defaultValue) so pressing Enter returns the intended default.

Suggested change

	ShowDefaultValue = false,
	ShowDefaultValue = false,
	DefaultValue = defaultValue,

[Copilot]

This change alters interactive prompt rendering/behavior but there are no tests validating the new [Y/n] formatting or the default-value semantics (Enter should select the configured default). Consider adding a focused unit test around ConfirmAsync similar to the existing ConsoleInteractionServiceTests patterns to prevent regressions.