Hooks have not initialized keepers because of incorrect ordering of initialization in app.go

[yurivin]

Describe the bug
Hooks have keepers not initialized because scaffold command does not has correct order of keepers & hooks initialization.

1. We have staking hooks in default scaffolded chain.
2. Newly scaffolded module code generates after default staking hooks initialization.
3. Once we add staking hooks for a new module, hooks does not have keepers initialized, because ordering of initialization in app.go affects the state.

To reproduce
Steps to reproduce the behavior:

1. Scaffold new chain
2. Scaffold new module
3. Add staking hook for a new module
4. Debug/test new hook with call to keeper.

What version are you using?

$ ignite version
Ignite CLI version:	v0.25.1
Ignite CLI build date:	2022-10-20T15:52:00Z
Ignite CLI source hash:	cc393a9b59a8792b256432fafb472e5ac0738f7c
Cosmos SDK version:	v0.46.3
Your OS:		                linux
Your arch:		        amd64
Your Node.js version:	v16.17.1
Your go version:	       go version go1.19.2 linux/amd64
Your uname -a:	       Linux  5.15.0-52-generic #58-Ubuntu SMP Thu Oct 13 08:03:55 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Possible solution

1. Manage to separate keepers & hooks initialization in app.go. So new modules initialization code always generated before hooks configuration in app.go including default hooks required by cosmos-sdk.