getRtlScrollAxisType detects incorrect RtlScrollAxisType for chrome

### Is this a regression?

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

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

_No response_

### Description

I recently upgraded to Angular ~16.2.10, and noticed that cdk-virtual-scroll-viewport is not working in RTL mode for horizontal scroll. Initial data is rendered but then on scroll subsequent records are not rendered.

On investigations I came to know that getRtlScrollAxisType is returning 2 (Inverted) instead of 1 (Negated). If I make it return 1 during debug, things start to work fine.

### Reproduction

StackBlitz link: https://stackblitz.com/edit/angular-yehn5j?file=src%2Fapp%2Fcdk-platform-overview-example.html
Steps to reproduce:
Notice that at the bottom of information, getRtlScrollAxisType is 2

### Expected Behavior

getRtlScrollAxisType() should return 1 for chrome.

### Actual Behavior

getRtlScrollAxisType() returns 2 for chrome

### Environment

- Angular: ~16.2.10
- CDK/Material: ~16.2.10
- Browser(s): Chrome 119.0.6045.160, Chrome 119.0.6045.200
- Operating System (e.g. Windows, macOS, Ubuntu): Windows 10 Pro

Comienza localizando getRtlScrollAxisType en el código de CDK platform o de scrolling y reproduce el fallo de desplazamiento horizontal RTL usando el ejemplo enlazado de StackBlitz en Chrome. Verifica el tipo de eje detectado y confirma que cdk-virtual-scroll-viewport renderiza correctamente los registros posteriores, manteniendo el comportamiento en los demás navegadores compatibles.

Escrito por el modelo de indexación a partir del texto del issue.