prepare mainnet chainspec

[dariolina]

I have modified taurus-compiled to mainnet-compiled to build the spec, removed genesis domains and included the bootstrap nodes we prepared on infra side.
Effectively, by including the JSON we now carry 2 copies of genesis allocations information, which is not ideal. I would like to keep it as is for the next days, however.

Code contributor checklist:

• I have read, understood and followed contributing guide

[NingLin-P]

Make sense.

One nit about the chain-spec-raw-mainnit.json file, I wonder if we should build this file publicly in CI for transparency to the community. Although I have locally compiled the binary from this branch and built the chain spec which is exactly the same as the chain spec this PR brought except for one key 0x3a636f6465 in the genesis state, which is probably the runtime code.

[dariolina]

How would I specify non-default bootstrap nodes to build it CI?

[NingLin-P]

How would I specify non-default bootstrap nodes to build it CI?

We will need 2 PRs, the first PR modifies taurus-compiled to mainnet-compiled, we build the chain spec in CI, and then the second PR brings the resulting chain spec file and adds the bootstrap node to it.

[dariolina]

Ok. I can do that!

[NingLin-P]

BTW, we probably also need to change taurus-compiled to mainnet-compiled in the CI workload in the first PR:

subspace/.github/workflows/chain-spec-snapshot-build.yml

Lines 31 to 32 in 867cb20

	docker run --rm -u root ${{ steps.build.outputs.digest }} build-spec --chain taurus-compiled --disable-default-bootnode > chain-spec-taurus.json
	docker run --rm -u root ${{ steps.build.outputs.digest }} build-spec --chain taurus-compiled --disable-default-bootnode --raw > chain-spec-raw-taurus.json

[dariolina]

I was going to do that after this one separately.
I can modify this one to rename in CI and the function (without JSON) and make a separate one for json