test collator-selection on rococo

[brenzi]

Test this PR: polkadot-fellows/runtimes#270

• upgrade and migration works, injecting invulnerables: producing blocks after mig without changing any keys
• invulnerables get ROC fees. (accounts must be created to get rewards: send 0.001 ROC)
• rotate session keys for collators
  • curl -H "Content-Type: application/json" -d '{"id":1, "jsonrpc":"2.0", "method": "author_rotateKeys", "params": [] }' http://localhost:9933/
  • setKey (need to wait for next session to take effect...)
  • session.nextKeys is indeed set to new session key for collator01 at next session
• sync new collator and apply as candidate
  • curl -H "Content-Type: application/json" -d '{"id":1, "jsonrpc":"2.0", "method": "author_rotateKeys", "params": [] }' http://localhost:9403/ -> 0x14a9ce066467dca785df80d4eebe31d68bd42683a4d304c4c90e20a9d6811d63
  • send 10 ROC to candidate
  • session.setKeys
  • collatorSelection.registerAsCandidate will lock 5 ROC deposit
  • council setDesiredCandidates(3) propose
  • new collator proposes blocks (wait for next session)

[brenzi]

[brenzi]

had to remove collator candidate because it missed producing blocks when it should've
re-registering candidacy and waiting for the next session + some time (see collator candidate "first block" which gets set into future