feat: add devnet custom genesis, aura and grandpa support

[kratico]

Resolves #889

How to test?

• for aura and grandpa, compile substrate node-template
• execute the following script

import { bins, net } from "./mod.ts"

const controller = new AbortController()

Deno.addSignalListener("SIGTERM", () => controller.abort())
Deno.addSignalListener("SIGINT", () => controller.abort())

const bin = bins({
  nodeTemplate: "/Users/parity/ghq/github.com/paritytech/substrate/target/release/node-template",
})

const relay = net.dev({
  bin: bin.nodeTemplate,
  chain: "local",
  customize(chainSpec) {
    // @ts-ignore
    chainSpec.genesis.runtime.sudo.key = "5FHneW46xGXgs5mUiveU4sbTyGBzmstUspZC92UhjJM694ty"
  },
})
relay.name = "relay"

console.log(await relay.spawnNet(controller.signal, await Deno.makeTempDirSync({ dir: "./tmp" })))

• check the logs ./tmp/cbfda8c3/relay/alice/stderr and validate that blocks are produced and finalized
• check the sudo key is 5FHneW46xGXgs5mUiveU4sbTyGBzmstUspZC92UhjJM694ty (or await chain.Sudo.Key.value())

[kratico]

@harrysolovay @tjjfvi
Given that the pallet name could be aliased to any string, Shall I implement an option to pass an optional genesis config in DevChainConfig?
This genesis config will be merged with chain spec genesis config.

For example, Moonbean manages consensus with their pallet-author-mapping and sets an AuthorMapping attribute in construct_rutime.
In the capi.config.ts, we could have something like

{
  binary: ...,
  chain: "...",
  genesis: { ... },
}

[harrysolovay]

That seems like a good path, but not necessarily expressing it in the TS. What's the most likely user story? Given that devs will generate the chainspec for their target chain, maybe they could pass the entire chainspec str, from which we'd extract the genesis config? Any simpler way to go about this?

[kratico]

That seems like a good path, but not necessarily expressing it in the TS. What's the most likely user story? Given that devs will generate the chainspec for their target chain, maybe they could pass the entire chainspec str, from which we'd extract the genesis config? Any simpler way to go about this?

For this story, I would just merge a custom genesis with the default genesis generated from the binary chain spec (for example, polkadot build-spec --chain rococo-local).

On the other hand, if devs pass a chainspec, I would just use that chainspec, add the bootnodes and use the genesis from that chainspec. For this, I would assume that the dev has already customized the genesis for their needs.