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/unit/application/collections/NoUnintentedInlining.spec.ts

@@ -1,6 +1,7 @@
 import { readdirSync, readFileSync } from 'fs';
 import { resolve, join, basename } from 'path';
 import { describe, it, expect } from 'vitest';
+import { formatAssertionMessage } from '@tests/shared/FormatAssertionMessage';
 
 /*
   A common mistake when working with yaml files to forget mentioning that a value should
@@ -24,11 +25,10 @@ describe('collection files to have no unintended inlining', () => {
       // act
       const lines = await findBadLineNumbers(testCase.content);
       // assert
-      expect(lines).to.be.have.lengthOf(0, printMessage());
-      function printMessage(): string {
-        return 'Did you intend to have multi-lined string in lines: ' // eslint-disable-line prefer-template
-          + lines.map(((line) => line.toString())).join(', ');
-      }
+      expect(lines).to.be.have.lengthOf(0, formatAssertionMessage([
+        'Did you intend to have multi-lined string in lines: ',
+        lines.map(((line) => line.toString())).join(', '),
+      ]));
     });
   }
 });