Increase scheduler’s max allowed weight to unblock extrinsics via governance

[chrisli30]

Description

We recently found that council.setMembers() extrinsic couldn’t successfully due to scheduler’spermenantlyOverweight error during governance referendum execution. This issue started to happen after Turing’s v1.9.0 release mostly due to the introduction of proofSize in Weight struct.

The solution is to change the below constant variable so it’s updated during the next release.

Turing’s current calculation:
https://github.com/OAK-Foundation/OAK-blockchain/blob/0ebac6996c25d8d721bc34912adba39d5e595b6d/runtime/turing/src/lib.rs#L747

Shiden’s calculation for reference:
https://github.com/AstarNetwork/Astar/blob/c9afb955bbed7afb7158899737505a8c6cc3a2a2/runtime/shiden/src/lib.rs#L173

I think we can just increase the percentage, currently at 10%, to higher to approximately equate to 2,048,000 proofsize.

Steps to Reproduce

https://polkadot.js.org/apps/#/explorer/query/0xa66312c8b29966a47059aa63dc53cdb1f36b674c9b5183723520fd07be1bd4c7

Expected vs. Actual Behavior

A simiple council.setMembers() call should pass and not encounter scheduler.permenantlyOverweight error.

Environment

The issue was found on Turing Staging.

[chrisli30]

The fix has been tested on Staging with v1.9.0.2. We’ll deploy it to Turing next week.

[chrisli30]

1.9.0.2 runtime 294 has been pushed to Turing Network. This issue is solved.