[Alert] Add prop to prioritize a component in the queue

[geospatialem]

Check existing issues

• I have checked for existing issues to avoid duplicates

Description

Current behavior of the component's queue is causing customer confusion is some scenarios and workflows.

We should provide a prop (name tbd) when a low-priority alert is already visible, and a higher impact alert that is very important to the user's workflow needs to be displayed. When enabled, the low priority alert would be rendered behind the current alert.

Acceptance Criteria

• Developer can modify the priority of one alert to become a high priority over another
• Enforce an alert to display with its priority

Relevant Info

• The user may not see the alert if a lower impact alert is already open (see Enhancement: calcite-alert - options for seeing queued messages without dismissing them #2835).
• Refer to calcite-alert: allow control over behavior of alerts in the Queue #8316 for the original request, and a more in-depth API issue

Which Component

alert

Example Use Case

1. An alert is showing at the bottom of the screen telling the user a new feature is now available.
2. The user does not dismiss this, they just ignore it
3. The user is taking a critical action and an error occurs
4. The error alert is behind the first alert, and they don't know what is wrong as the meaningful information is hidden

Priority impact

p3 - want for upcoming milestone

Calcite package

• @esri/calcite-components
• @esri/calcite-components-angular
• @esri/calcite-components-react
• @esri/calcite-design-tokens
• @esri/eslint-plugin-calcite-components

Esri team

ArcGIS Online

[macandcheese]

This could be a high-priority boolean that replaces the top-most (currently open) Alert immediately, or it could also be a property like urgency or queue-type / queue-strategy that accepted values to: "replace the top-most", "add to stack immediately behind top-most", or "add to back of stack (current / default behavior).