Reset subsystem status

[badrogger]

Description

To prevent skale admin restarting skaled while database is being opened, it will utilise subsystemRunning section from skaled.status file. In particular Rpc field. To make sure that the field is false before rpc server is initialized, after skaled is started, Rpc and Blockchain fields are reseted.
Related skale-admin pr: skalenetwork/skale-admin#1143

Tests

Additional tests added in StatusAndControlTest.cpp to cover status file operations.
The new behaviour was verified on local network as well as using standalone mode.

Performance Impact

All changes are related to skaled initialization procedure where only order of operation is changed.
No performance related changes were made.

[github-actions]

SUGGESTIONS BEFORE MERGE:

1. Build custom container here: https://github.com/skalenetwork/skaled/actions?query=workflow%3A%22Custom+Docker+and+Binary%22
2. Test it here: https://github.com/skalenetwork/skale-ci-integration_tests/actions?query=workflow%3A%22Skaled+Nightly+Tests%22
3. Edit VERSION file appropriately to your changes!
   See https://skalelabs.atlassian.net/wiki/spaces/SKALE/pages/2444951553/Branching+instructions