Make RWLock Write-Preferring

[CMCDragonkai]

Description

Right now the RWLock based on https://gist.github.com/CMCDragonkai/4de5c1526fc58dac259e321db8cf5331 is read-preferring.

This means on blocking methods, such as the compose method in the networking domain, concurrent pressure can starve the stop operation.

Changing to write-preferring RWLock allows us to ensure that we can call stop and interrupt any of the blocking decorated methods. This is more robust for denial of service and preventing long-shutdowns.

Any other concurrent calls should then throw an exception once stop has interrupted them.

Note that this is not the same as the abort signal. Calling stop cannot abort asynchronous operations atm. Any locked async operation is still waited to be completed.

Aborting would require more study and research in MatrixAI/Polykey#297

Issues Fixed

• Relates to Adding QA jobs and expanding test jobs for CI/CD. Polykey#292 and the usage of blocking methods for networking domain.

Tasks

1. Upgraded the RWLock to write-preferring
2. Tested the RWLock
3. Added stop or destroy interruption tests to class decorators

Final checklist

• Domain specific tests
• Full tests
• Updated inline-comment documentation
• Lint fixed
• Squash and rebased
• Sanity check the final build