bug(Material Stepper): Certain ARIA roles must contain particular children Error

### Is this a regression?

- [ ] Yes, this behavior used to work in the previous version

### The previous version in which this bug was not present was

_No response_

### Description

The documentation for the stepper appears to indicate that this should not be occurring based on the role for the stepper being a tablist and the roles for steps being tab. I think the problem comes from some interim nodes between the tabs and the tablist.

### Reproduction

Steps to reproduce:
1. navigate to the material stepper examples page: https://rc.material.angular.io/components/stepper/examples
2. run a scan of it using the axe def tool chrome extension: https://chrome.google.com/webstore/detail/axe-devtools-web-accessib/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US
3. You will see that it will result in 14 instances of the error "Certain ARIA roles must contain particular children". That is one for each stepper on the example page.

### Expected Behavior

Running the WCAG2.1 AA compliance scan should not find the "Certain ARIA roles must contain particular children" issue which is considered a critical aria issue.

### Actual Behavior

Running the WCAG2.1 AA compliance scan finds the "Certain ARIA roles must contain particular children" issue which is considered a critical aria issue.

There is no clear way to resolve this issue with the stepper component.

### Environment

- Angular: 15
- CDK/Material: 15.1.0
- Browser(s): Chrome
- Operating System (e.g. Windows, macOS, Ubuntu): Windows

Start with the Angular Material stepper examples page and reproduce the issue using the axe DevTools Chrome extension. Inspect the stepper's rendered ARIA roles and the interim nodes between the tablist and its tab children. Done means the WCAG 2.1 AA scan no longer reports "Certain ARIA roles must contain particular children" for the examples.

Written by the indexing model from the issue text.