refactor!: runtime context follow-up

[David-Petrov]

This is the follow-up PR of #456

Each commit in this PR more or less tackles an aforementioned dangling issue discussion from the previous PR.

I suggest this PR would be easier reviewed commit per commit, since the entirety of file changes doesn't necessarily paint a coherent picture.

---

A detailed map to the previous issues:

• a395403 resolves https://github.com/LimeChain/Fruzhin/pull/456#discussion_r1631276229
• e222d87 fixes
  • https://github.com/LimeChain/Fruzhin/pull/456#discussion_r1623948424
  • https://github.com/LimeChain/Fruzhin/pull/456#discussion_r1624225562
  • https://github.com/LimeChain/Fruzhin/pull/456#discussion_r1622268179
  • https://github.com/LimeChain/Fruzhin/pull/456#discussion_r1622273420
• 66991d2 fixes https://github.com/LimeChain/Fruzhin/pull/456#discussion_r1622220414
• 43db682 resolves https://github.com/LimeChain/Fruzhin/pull/456#discussion_r1622192678

[sonarcloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud