bug(Table): Tab navigation on inputs inside table with sticky columns (focus out of sight)

### 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

When having multiple inputs on one row, one input per cell, inside a table with one or more sticky columns the TAB key navigation is focusing at some point on an input that is hidden under the sticky columns, making the focus out of sight, but still inside the table.

The current behavior it's not compliant with the latest accessibility guidelines (WCAG) that states that an element that is focused needs to be in sight. (ref link: https://www.w3.org/WAI/WCAG22/Understanding/focus-not-obscured-minimum)

### Reproduction

StackBlitz link:
https://stackblitz.com/edit/r22tvc?file=src%2Fexample%2Ftable-sticky-complex-flex-example.html

Table state:
- have horizontal scroll (requires a higher number of columns)
- one or more columns sticky
- on at least one row have an input on each cell

Steps to reproduce:
1. Scroll the table in order to hide some columns under the sticky columns
2. Focus first inside the first cell of the row with the inputs
3. Press TAB key in order to navigate through the inputs
4. The focus at some point is on the input that is hidden under the sticky columns

### Expected Behavior

The focused element should be in sight, visible, not hidden under the sticky columns.

### Actual Behavior

The focus is hidden under the sticky columns, out of sight.

DEMO:

### Environment

- Angular: 16.1.1
- CDK/Material: 16.2.9
- Browser(s): Chrome (118.0.5993.89) / Firefix (119.0)
- Operating System (e.g. Windows, macOS, Ubuntu): Windows x64

Commencez avec la reproduction StackBlitz dans src/example/table-sticky-complex-flex-example.html et reproduisez le problème en utilisant le défilement horizontal, des colonnes sticky et des champs de saisie sur une même ligne. Vérifiez la correction en parcourant chaque champ de saisie avec la touche Tab et en confirmant que l’élément ciblé reste visible au lieu d’être masqué par les colonnes sticky.

Rédigé par le modèle d'indexation à partir du texte de l'issue.