Rename MessageBar interaction to Notification

[JamesNK]

Description

Rename message bar to notification. Feedback from user.

Addresses #10427

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
    • Link to aspire-docs issue (consider using one of the following templates):
      • New (or update) doc-idea template
      • New breaking-change template
      • New diagnostic template
  • No

[Copilot]

Pull Request Overview

This PR renames "MessageBar" to "Notification" throughout the Aspire codebase to improve naming clarity based on user feedback. The change affects the interaction service API and all related components.

Key changes:

• Renamed PromptMessageBarAsync method to PromptNotificationAsync across all implementations
• Updated class names from MessageBarInteractionOptions to NotificationInteractionOptions and MessageBarInteractionInfo to NotificationInteractionInfo
• Modified protobuf definitions to use InteractionNotification instead of InteractionMessageBar

Reviewed Changes

Copilot reviewed 12 out of 12 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
src/Aspire.Hosting/IInteractionService.cs	Updated interface method signature and class names for notification interactions
src/Aspire.Hosting/InteractionService.cs	Renamed implementation methods and internal classes from MessageBar to Notification
src/Aspire.Hosting/Dashboard/proto/dashboard_service.proto	Updated protobuf message definitions and field names for notifications
src/Aspire.Hosting/Dashboard/DashboardService.cs	Updated service implementation to use new notification class names
src/Aspire.Hosting/Dashboard/DashboardServiceData.cs	Updated request handling to use notification instead of message bar
src/Aspire.Dashboard/Components/Interactions/InteractionsProvider.cs	Updated dashboard component to handle notification interactions
src/Aspire.Hosting/VersionChecking/VersionCheckService.cs	Updated method calls to use new notification API
src/Aspire.Hosting/Orchestrator/ParameterProcessor.cs	Updated method calls to use new notification API
src/Aspire.Hosting.Azure/Provisioning/Internal/DefaultProvisioningContextProvider.cs	Updated method calls to use new notification API
tests/Shared/TestInteractionService.cs	Updated test implementation method signature
tests/Aspire.Hosting.Tests/InteractionServiceTests.cs	Updated test method calls
playground/Stress/Stress.AppHost/InteractionCommands.cs	Updated playground examples to use new notification API

Comments suppressed due to low confidence (2)

src/Aspire.Hosting/Dashboard/proto/dashboard_service.proto:361

• [nitpick] The field name should use camelCase instead of snake_case to be consistent with other protobuf field naming conventions in the codebase.

    string link_text = 3;

src/Aspire.Hosting/Dashboard/proto/dashboard_service.proto:362

• [nitpick] The field name should use camelCase instead of snake_case to be consistent with other protobuf field naming conventions in the codebase.

    string link_url = 4;

[JamesNK]

/backport to release/9.4

[github-actions]

Started backporting to release/9.4: https://github.com/dotnet/aspire/actions/runs/16312952806