feat(runtime)!: use async marine [fixes VM-365,NET-758,NET-757]

[ValeryAntopol]

Description

Introduce async marine runtime.

Motivation

[Explain why these changes are necessary or beneficial. Discuss any problems or limitations with the current implementation that this pull request addresses.]

Related Issue(s)

VM-365
NET-758
NET-757

Additional Notes

• increase threads requirements for some tests
• introduced a shared wasm backend for all AVM instances instead of creating it for each AVM instance
• a separate marine config for AVM & services
• move to async calls where it needed
• added a new option for the test client with disabled reconnection
• fixed the graceful shutdown for the nox process
• moved ServicesConfig to particle-services crate and renamed to ParticleAppServicesConfig
• refactored Init flow for the system-services

Checklist

• The code follows the project's coding conventions and style guidelines.
• All tests related to the changes have passed successfully.
• Documentation has been updated to reflect the changes (if applicable).
• All new and existing unit tests have passed.
• I have self-reviewed my code and ensured its quality.
• I have added/updated necessary comments to aid understanding.

Reviewer Checklist

• Code has been reviewed for quality and adherence to guidelines.
• Tests have been reviewed and are sufficient to validate the changes.
• Documentation has been reviewed and is up to date.
• Any questions or concerns have been addressed.

[linear]

VM-365 integrate async marine and avm-server into Nox

NET-757 Integrate async marine into Nox w/o epochs

NET-758 Integrate marine epoch interruptions into Nox