NEXT: Resolve regressions in the component unit tests

[endigo9740]

Following the recent integration of Zag, this introduced a number of changes that broken a various React component unit tests. We should make it a priority to restore these asap.

Goals

1. Ensure we're only testing Skeleton-provided features. Zag is responsible for testing their features.
2. We should prune all invalid test cases that do not confirm to the goal above.
3. We should ensure all remaining tests are back in a working state.
4. If possible we should aim to improve our test quality and coverage while we're at it.
5. Provide test cases for components currently lacking a test spec

Progress:

NOTE: AppBar and Navigation do not implement Zag but still need test cases.

Component	Status	Owner
Accordion	✅	Hugo
AppBar*	✅	Hugo
Avatar	✅	Hugo
Navigation*	✅	Hugo
Progress	✅	Hugo
Progress Ring	✅	Chris
Rating	✅	Chris
Seg. Control	✅	Chris
Switch	✅	Chris
Tabs	✅	Chris

[endigo9740]

@Hugos68 given the number of components I'm open to divvy this up in some manner. We should prioritize this above any other tasks. I wouldn't be opposed to revisit testing for Svelte components again either.

[endigo9740]

Handled by:

• NEXT: Resolve Unit Tests - Part 1 #2813
• NEXT: Resolve Unit Tests - Part 2 #2814