Remove regen module manager and use SDK App Module

[robert-zaremba]

Summary

Our custom App Module type and Configurator doesn't have any benefits compared to the SDK 0.46 App Module.
Let's remove it and migrate fully to SDK Module manager.

Problem Definition

Regen custom Configurator and App module was an experiment. It doesn't have enough benefits and it introduces additions maintenance costs and complexity

---

For Admin Use

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

[ryanchristo]

Is this necessary for the v4.0 upgrade? Should we maybe discuss this before putting it into the ready column?

[aaronc]

Agreed, but not sure we should worry about this for 4.0. With the new app wiring we'll want to migrate anyway when that's ready

[robert-zaremba]

I would put it as nice to have.
BTW, @ryanchristo why did you remove Api Breaking label? This task is about removing the whole public package, so it's API breaking.

[ryanchristo]

I would put it as nice to have.

I already moved it to the new v5.0 epic and milestone. We can assess whether nice to have in that context at a later point in time since we are no longer planning to upgrade to Cosmos SDK v0.46 for the v4.0 release.

why did you remove Api Breaking label?

This label was originally created for pull requests. I created it back when we were transitioning to semantic commits. We could use it for issues too but if we start actively using it for all issues it might add more clutter than necessary to the board. We should probably reasses our labels and make sure we are consistently using them.

Let's maybe further discuss on our extended standup on Thursday.

[robert-zaremba]

moved discussion to Discord. I'm in a strong favor to keep labels. Github is our primary tool