feat!: Provide logger through depinject

[facundomedica]

Description

What is proposed here is that we pass in the logger using depinject.Supply instead of through the AppBuilder's Build method. The bank module was modified as an example.

Ref: #14683

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• included the correct type prefix in the PR title
• added ! to the type prefix if API or client breaking change
• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• followed the guidelines for building modules
• included the necessary unit and integration tests
• added a changelog entry to CHANGELOG.md
• included comments for documenting Go code
• updated the relevant documentation or specification
• reviewed "Files changed" and left comments if necessary
• confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed the correct type prefix in the PR title
• confirmed ! in the type prefix if API or client breaking change
• confirmed all author checklist items have been addressed
• reviewed state machine logic
• reviewed API design and naming
• reviewed documentation is accurate
• reviewed tests and test coverage
• manually tested (if applicable)

[tac0turtle]

i dont think this is needed, we can just pass the logger from cosmossdk.io/logger which is instantiated already

[julienrbrt]

Mostly lgtm. Is there an issue to track the fact that we should do that for all modules?

[julienrbrt]

lgtm! But I think still we need an issue for not forgetting to do that in other modules.