Epic: Refactor/restructure sorting across components

[geospatialem]

Description

Restructure/refactor the sorting component to support components across the design system, similar to the structure currently setup on block, where the parent supports the child component sorting.

Additional considerations include:

• keyboard support
• AT and keyboard support, in particular for Windows AT, JAWS and NVDA

Proposed Advantages

Consistent approaches across components, such as:

1. A consistent story/implementation across components
2. Setting sorting on the parent component
3. Wiring up keyboard functionality consistently across the design system for keyboard and AT users

Which Component

• block
• list
• tree - lower priority/future (?)
• chip-group - lower priority/future (?)

Relevant Info

Came up as part of a discussion from #7445 via https://github.com/Esri/calcite-design-system/issues/7445#issuecomment-1688961553

Related: https://github.com/Esri/calcite-design-system/issues/7426

Calcite package

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

[geospatialem]

Research spike to determine next steps for sorting across the design system. Some considerations:

• Do we want to provide a sorting utility?
• Should we consider sorting on the block component? We have previously had some support on the capability for teams