Container candidates in dev service

[girazoki]

Adds the ability to inject container candidates on dancelights dev service. For now this remains as an opt-in that you can enable in your tests by calling the following rpc in dev mode:

• mock_enableParaInherentCandidate

similarly you can disable it by calling:

• mock_disableParaInherentCandidate

I also added a test that proves that when enabled, this mode makes the para-head progress in the relay, indicating the candidates are being inserted.

TODO in this PR:

• Cleanup
• tests with rewards being stored

Follow-up tests for future PRs would be:

• AuthorNoting properly tested: now that we can inject proper headers, we should be able to properly test author-noting inherent, since we need the header to retrieve the author.
• XCM tests: now that we have the ability to inject candidates we should also be able to put UMP messages in the candidates.

[github-actions]

WASM runtime size check:

Compared to target branch

dancebox runtime: 1412 KB (no changes) ✅

flashbox runtime: 832 KB (no changes) ✅

dancelight runtime: 2008 KB (+2008 KB) ⚠️

container chain template simple runtime: 1088 KB (-4224 KB) ✅

container chain template frontier runtime: 1388 KB (-5136 KB) ✅

[github-actions]

Coverage Report

(master)

@@                      Coverage Diff                      @@
##           master   girazoki-dev-service-comp      +/-   ##
=============================================================
+ Coverage   65.33%                      65.47%   +0.14%     
+ Files         311                         312       +1     
+ Lines       54198                       54503     +305     
=============================================================
+ Hits        35407                       35685     +278     
+ Misses      18791                       18818      +27     

Files Changed	Coverage
/solo-chains/node/tanssi-relay-service/src/dev_service.rs	91.57% (+3.29%)	✅

Coverage generated Fri Nov 22 14:45:35 UTC 2024