Increase timeout for test_lock_contention on RISC-V

[Gui-Yue]

This PR addresses a test failure for tests.handlers.test_worker_lock.WorkerLockTestCase.test_lock_contention which consistently times out on the RISC-V (specifically riscv64) architecture.

The test simulates high lock contention and has a default timeout of 5 seconds, which seems sufficient for architectures like x86_64 but proves too short for current RISC-V hardware/environment performance characteristics, leading to spurious tests.utils.TestTimeout failures.

This fix introduces architecture detection using platform.machine(). If a RISC-V architecture is detected:

• The timeout for this specific test is increased (e.g., to 15 seconds ).

The original, stricter timeout (5 seconds) and lock count (500) are maintained for all other architectures to avoid masking potential performance regressions elsewhere.

This change has been tested locally on RISC-V, where the test now passes reliably, and on x86_64, where it continues to pass with the original constraints.

---

Pull Request Checklist

• Pull request is based on the develop branch (Assuming you based it correctly)
• Pull request includes a changelog file. (See below)
• Code style is correct (run the linters) (Please run linters locally)

[CLAassistant]

All committers have signed the CLA.