Fix touch state not being activated in iOS Safari

This commit resolves the issue with the `:active` pseudo-class not
activating in mobile Safari on iOS devices. It introduces a workaround
specifically for mobile Safari on iOS/iPadOS to enable the `:active`
pseudo-class. This ensures a consistent and responsive user interface
in response to touch states on mobile Safari.

Other supporting changes:

- Introduce new test utility functions such as `createWindowEventSpies`
  and `formatAssertionMessage` to improve code reusability and
  maintainability.
- Improve browser detection:
  - Add detection for iPadOS and Windows 10 Mobile.
  - Add touch support detection to correctly determine iPadOS vs macOS.
  - Fix misidentification of some Windows 10 Mobile platforms as Windows
    Phone.
  - Improve test coverage and refactor tests.

tests/e2e/modal-layout-shifts.cy.ts

@@ -1,3 +1,4 @@
+import { formatAssertionMessage } from '@tests/shared/FormatAssertionMessage';
 import { ViewportTestScenarios } from './support/scenarios/viewport-test-scenarios';
 
 describe('Modal interaction and layout stability', () => {
@@ -24,10 +25,10 @@ describe('Modal interaction and layout stability', () => {
 
       captureViewportMetrics((metrics) => {
         const metricsAfterModal = metrics;
-        expect(metricsBeforeModal).to.deep.equal(metricsAfterModal, [
+        expect(metricsBeforeModal).to.deep.equal(metricsAfterModal, formatAssertionMessage([
           `Expected (initial metrics before modal): ${JSON.stringify(metricsBeforeModal)}`,
           `Actual (metrics after modal is opened): ${JSON.stringify(metricsAfterModal)}`,
-        ].join('\n'));
+        ]));
       });
     });
   });