feat: add solana monitoring data

[marcellorigotti]

Pull Request

Closes: PRO-1658

Checklist

Please conduct a thorough self-review before opening the PR.

• I am confident that the code works.
• I have written sufficient tests.
• I have written and tested required migrations.
• I have updated documentation where appropriate.

Summary

Add solana monitoring data to monitoring rpc:

• Available nonces/Unavailable nonces
• Broadcaster.incomingKeyAndBroadcastId() -> This is missing for all the chains
  • Plus the signature of the transaction for solana -> we need to check it didn't revert
• Solana aggKey
• SolanaBroadcaster.currentOnChainKey -> Sol funds held here

[codecov]

Codecov Report

Attention: Patch coverage is 10.25641% with 35 lines in your changes missing coverage. Please review.

Project coverage is 70%. Comparing base (e7c9706) to head (249d530).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
state-chain/runtime/src/lib.rs	0%	0 Missing and 29 partials ⚠️
state-chain/custom-rpc/src/lib.rs	0%	4 Missing ⚠️
state-chain/runtime/src/monitoring_apis.rs	67%	0 Missing and 2 partials ⚠️

Additional details and impacted files

@@          Coverage Diff           @@
##            main   #5277    +/-   ##
======================================
- Coverage     70%     70%    -0%     
======================================
  Files        487     487            
  Lines      87463   87358   -105     
  Branches   87463   87358   -105     
======================================
- Hits       61511   61313   -198     
- Misses     22672   22730    +58     
- Partials    3280    3315    +35     

Flag	Coverage Δ
	70% <10%> (-<1%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[dandanlen]

Looks fine to me, i'd just like to understand better how this will be used. Let's chat tomorrow.

[marcellorigotti]

Looks fine to me, i'd just like to understand better how this will be used. Let's chat tomorrow.

These changes are also breaking, bringing the same problems as #5279 does, correct?

[dandanlen]

To summarize:

• New node with old runtime will be broken.
• Old node with new runtime will be ok.

So we can update the monitoring rpc node after the runtime upgrade and we should be ok. However @marcellorigotti is looking into how best to manage this so that we can update the node ahead of time.