fix(runtime): PreBlocker getting overwritten if set as a baseapp option

[facundomedica]

Description

---

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
• run make lint and make test
• 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]

is this a blocker for 0.50

[julienrbrt]

is this a blocker for 0.50

Yes, it is already set here, and we should have an if-check to verify that it isn't already set in baseapp.

[github-actions]

@facundomedica your pull request is missing a changelog!

[facundomedica]

We might have to do the same for Begin/EndBlock depending on use cases.
Also maybe think about passing txs to the modules' PreBlocker that way we wouldn't need a global Preblocker but we could leave that to each module.
On the other hand, PrepareProposal, VoteExtensions and such are part of baseapp and modules can't access that, so the creation of the injected tx we use in VE is being that at a "global" level, so it might not make sense to do it at a module's level.

[julienrbrt]

lgtm!

[julienrbrt]

Agree to not have this in module level, as it quite complexify the API and may lead to some hacky things done by modules.