add extrinsic_state_version to RuntimeVersion and bump CoreApi version to 5

[vedhavyas]

Description

• What does this PR do?
  Adds extrinsic_state_version field to RuntimeVersion so that projects can pick V0/V1 depending on the use case.
• Why are these changes needed?
  Currently extrinsic root is derived using StateVersion::V0. In order to generate the extrinsic root, we would need to have access to full extrinsic data. We have a use case where, domains extrinsic root need to be derived on consensus runtime and passing all the extrinsic data through Fraud proof will exceed block limit. We are planning to use StateVersion::V1 so that we can just use extrinsic hashes if the extrinsic data is more than 32 bytes.
• How were these changes implemented and what do they affect?
  Field extrinsic_state_version is added to RuntimeVersion struct and CoreApi version is bumped to 5. CoreApi version < 5 always leads to StateVersion::V0 while CoreApi verision >= 5 can let projects to pick ether V0 or V1

Checklist

• My PR includes a detailed description as outlined in the "Description" section above
• My PR follows the labeling requirements of this project (at minimum one label for T
  required)
• I have made corresponding changes to the documentation (if applicable)
• I have added tests that prove my fix is effective or that my feature works (if applicable)

[tomaka]

Since it would modify Polkadot/Kusama, this change needs an RFC: https://github.com/polkadot-fellows/RFCs

[vedhavyas]

I have opened RFC here - polkadot-fellows/RFCs#42

Thanks for the heads up @tomaka

[nazar-pc]

The changes are simple, so I did a rebase on latest master

[tomaka]

Note that the PR no longer matches what the RFC says.

[nazar-pc]

Hm, true.
Ved will have another PR open that implements latest proposal, likely later this week.

[bkchr]

@vedhavyas do you still want to open a pr based on the RFC?

[vedhavyas]

@bkchr yes, I'm working on this right now. Should have a PR soon

[vedhavyas]

@bkchr The PR should be up here - #4257