[DO NOT MERGE] test: staking query not module query safe

[crodriguezvega]

Description

Opening this PR to show an issue we are trying to debug in ibc-go.

We are back porting ICA queries to release/v7.5.x and If we run our tests using go 1.19, then a test that checks that the staking queries are module safe queries fails. However, if we run the tests with go 1.22, then it passes... You can see the failure in the test of this PR here.

Closes: #XXXX

---

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
• confirmed ! in 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
• reviewed "Files changed" and left comments if necessary
• included the necessary unit and integration tests
• added a changelog entry to CHANGELOG.md
• updated the relevant documentation or specification, including comments for documenting Go code
• 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 all author checklist items have been addressed
• reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

[facundomedica]

1.19 and 1.20 fail, 1.21 and 1.22 passes. Also allowList has a length of 7 vs 32 when working correctly.

EDIT: Importing the package works _ "cosmossdk.io/api/cosmos/staking/v1beta1", now we have to find why it works differently

[facundomedica]

So far it seems that this is related to a change in how Go initializes packages: https://tip.golang.org/doc/go1.21

I can't find precisions on the previous behavior as it's "unspecified".

[tac0turtle]

closing this for now, we should open an issue to track it