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/Parser/Script/Compiler/Function/ExpectFunctionBodyType.ts

@@ -1,6 +1,7 @@
 import {
   CallFunctionBody, CodeFunctionBody, FunctionBodyType, SharedFunctionBody,
 } from '@/application/Parser/Script/Compiler/Function/ISharedFunction';
+import { formatAssertionMessage } from '@tests/shared/FormatAssertionMessage';
 
 export function expectCodeFunctionBody(
   body: SharedFunctionBody,
@@ -16,14 +17,9 @@ export function expectCallsFunctionBody(
 
 function expectBodyType(body: SharedFunctionBody, expectedType: FunctionBodyType) {
   const actualType = body.type;
-  expect(actualType).to.equal(
-    expectedType,
-    [
-      '\n---',
-      `Actual: ${FunctionBodyType[actualType]}`,
-      `Expected: ${FunctionBodyType[expectedType]}`,
-      `Body: ${JSON.stringify(body)}`,
-      '---\n\n',
-    ].join('\n'),
-  );
+  expect(actualType).to.equal(expectedType, formatAssertionMessage([
+    `Actual: ${FunctionBodyType[actualType]}`,
+    `Expected: ${FunctionBodyType[expectedType]}`,
+    `Body: ${JSON.stringify(body)}`,
+  ]));
 }