Future Breaking Changes

[joshwooding]

This is an umbrella issue to track changes for v2.

### Breaking Changes - AG-Grid Theme v3
- [ ] https://github.com/jpmorganchase/salt-ds/issues/4220
- [ ] Support new ag grid theming API (https://www.ag-grid.com/javascript-data-grid/theming-api/)

### Breaking Changes - Core
- [ ] Remove `separators` prop from `FlexLayout`
- [ ] #1335
- [ ] Card `interactive` prop
- [ ] Default style injection to false #2532
- [ ] Navigation Item: Remove wrapping `<div/>` so that NavigationItem renders either a `<button\>` or `<anchor/>`, this will enable us to pass `...rest` to the actual `<button\>` or `<anchor/>`, rather than to the wrapping `<div/>`. The breaking change is the Typescript types and the `ref`, which currently a `<div/>` . This change is now possible due to us adding a more customisable API through the `render` prop. #3417
- [ ] Remove `UNSTABLE_` backwards compatibility
- [ ] ViewportProvider #3265
- [ ] Use of `@media (hover: hover)`
- [ ] Formalize `--saltComponent-xyz` API (vs `--componet-xyz`)
- [ ] Investigate potential inclusion mentioning CSS layer, depends on whether minimum browser support can be bumped?

### Breaking Changes - Theme
- [ ] https://github.com/jpmorganchase/salt-ds/issues/4221

### Breaking Changes - Dependencies
- [ ] Bump up [minimum browser support](https://www.saltdesignsystem.com/salt/about/supported-platforms#browser)

### Breaking Changes - Icons
- [ ] Remove deprecated icons
- [ ] Remove aria-label and role by default

[el-dav]

I'd suggest removing the responsive behaviour that's built into layout components when we're doing V2. Alternative could be the spike I did on responsive props where consumers can wrap any component to make it responsive.

[mark-tate]

Agree date for breaking changes - current proposal is end of Q1/2025 Work should start in Q1 2025 Communication should start Q4/2025 - Review in Ristretto ?