Clean up genesis config presets for all runtimes

[seadanda]

This PR does three things related to chain-specs and genesis config presets:

• Refactor preset_names to genesis_config_presets in all runtimes as suggested for the Polkadot Coretime runtime in Add the Polkadot Coretime runtime #410.
• Make the chain-spec generator use the preset from the WASM directly for each runtime.
• Propagate the on_chain_release_build feature to the chain-spec generator. Without this we cannot generate live/genesis chain-specs with the chain-spec generator without having to post-process it to replace the WASM compiled with this flag.

[bkchr]

/merge

[fellowship-merge-bot]

Enabled auto-merge in Pull Request

Available commands

• /merge: Enables auto-merge for Pull Request
• /merge cancel: Cancels auto-merge for Pull Request
• /merge help: Shows this menu

For more information see the documentation

[fellowship-merge-bot]

Failed to update PR ❌

There was an error while trying to keep this PR up-to-date

You may have conflicts ‼️ or may have to manually sync it with the target branch 👉❇️

More info in the logs 📋

[seadanda]

/merge

[fellowship-merge-bot]

Enabled auto-merge in Pull Request

Available commands

• /merge: Enables auto-merge for Pull Request
• /merge cancel: Cancels auto-merge for Pull Request
• /merge help: Shows this menu

For more information see the documentation

[kianenigma]

Why does the fellowship repo have this chain-spec generator and not use OG chain-spec-builder?

Sorry of this is duplicate, I think I have heard an explanation of this recently, but I can't recall it.

[bkchr]

Why does the fellowship repo have this chain-spec generator and not use OG chain-spec-builder?

Historical reasons. We don't really need it anymore. Someone just needs to remove it.

[bkontur]

Why does the fellowship repo have this chain-spec generator and not use OG chain-spec-builder?

Sorry of this is duplicate, I think I have heard an explanation of this recently, but I can't recall it.

Historical reasons. We don't really need it anymore. Someone just needs to remove it.

@bkchr @kianenigma #395