Align timeouts on running tests in public CI on Linux (#2267)

The timeout was set up to 12 minutes in `Conda package` workflow.
That PR proposes to align it across all GitHub workflows where tests are
running on Linux.

Sometimes the current timeout of 10 minutes might not be enough (like
[here](https://github.com/IntelPython/dpnp/actions/runs/12870503193/job/35883466675?pr=2266)
in `Test oneMKL interfaces` workflow) which caused unexpected failure or
extra rerunning attempt.

Author: antonwolfy

.github/workflows/check-mkl-interfaces.yaml

@@ -108,7 +108,7 @@ jobs:
         id: run_tests
         uses: nick-fields/retry@7152eba30c6575329ac0576536151aca5a72780e # v3.0.0
         with:
-          timeout_minutes: 10
+          timeout_minutes: 12
           max_attempts: ${{ env.RUN_TESTS_MAX_ATTEMPTS }}
           retry_on: any
           command: |
@@ -216,7 +216,7 @@ jobs:
         id: run_tests
         uses: nick-fields/retry@7152eba30c6575329ac0576536151aca5a72780e # v3.0.0
         with:
-          timeout_minutes: 10
+          timeout_minutes: 12
           max_attempts: ${{ env.RUN_TESTS_MAX_ATTEMPTS }}
           retry_on: any
           command: |

.github/workflows/cron-run-tests.yaml

@@ -126,7 +126,7 @@ jobs:
         id: run_tests_linux
         uses: nick-fields/retry@7152eba30c6575329ac0576536151aca5a72780e # v3.0.0
         with:
-          timeout_minutes: 10
+          timeout_minutes: 12
           max_attempts: ${{ env.RUN_TESTS_MAX_ATTEMPTS }}
           retry_on: any
           command: |