Fix and refactore app options passing

[robert-zaremba]

Summary

We don't have a clear way how to pass app configuration down to packages and modules. Currently this is done through Context, globals and a global config.

Problem Definition

1. Putting things into Context obfuscates the parameters flow
2. Using mutable globals is even worse - we will loose a control on the app management
3. Using a global Config object with imports other packages to set concrete types is not usable - only few packages could be able to use it, all rest will be in a circular dependency check.

Ref: https://github.com/cosmos/cosmos-sdk/pull/8825/files#r595494865

Proposal

Consider:

• splitting package configuration into sub pacages (but not types)
• create object factories

---

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate contributors tagged
• Contributor assigned/self-assigned

[robert-zaremba]

cc: @gsora

[julienrbrt]

We've added a DynamicConfig in core: https://github.com/cosmos/cosmos-sdk/blob/main/core/server/config.go#L3-L8.
It is always the same as AppOptions where you can pass config (for modules).

The issue you link refers to the client context and the client APIs that are being simplified here: #20623