Seal global cosmos config outside of the cli

[evan-forbes]

to avoid breaking all the tests and increase diff from upstream in this repo, I think we should attempt a different approach where we only call the config/seal functions once in the app in some init function, then import something from that file in celestia-node. I think that will force us to only seal a single time, instead of once in the cli for app and node each.

Originally posted by @evan-forbes in celestiaorg/cosmos-sdk#297 (review)

[Wondertan]

Nice! We did almost the same recently. The PR name, though does not reflect what was in the final form, but I moved this init to one place in core pkg. Once you move this into the app, release and update the node with a PR, it would be nice to include the removal of init on our side.

[evan-forbes]

@vgonkivs currently we are sealing here

celestia-app/cmd/celestia-appd/cmd/root.go

Lines 51 to 55 in 0b447ad

	cfg := sdk.GetConfig()
	cfg.SetBech32PrefixForAccount(app.Bech32PrefixAccAddr, app.Bech32PrefixAccPub)
	cfg.SetBech32PrefixForValidator(app.Bech32PrefixValAddr, app.Bech32PrefixValPub)
	cfg.SetBech32PrefixForConsensusNode(app.Bech32PrefixConsAddr, app.Bech32PrefixConsPub)
	cfg.Seal()

I haven't tried this, but we can probably just include that in an init function in the app package. either directly in this file, or in its own