chore: upgrade wasmd to v0.28.0

[p0mvn]

Part of #2566

What is the purpose of the change

Upgrade wasmd to v0.28.0

Branch: https://github.com/osmosis-labs/wasmd/tree/v0.28.0x-osmo-v12
Tag: https://github.com/osmosis-labs/wasmd/releases/tag/v0.28.0-osmo-v12.1

Testing and Verifying

This change is a trivial rework / code cleanup without any test coverage.

Documentation and Release Note

• Does this pull request introduce a new feature or user-facing behavior changes? no
• Is a relevant changelog entry added to the Unreleased section in CHANGELOG.md? no
• How is the feature or change documented? not applicable

[p0mvn]

I've investigated the simulator failure, and it seems to be happening during fee validation in x/txfees:

osmosis/x/txfees/keeper/feetokens.go

Line 112 in 1d9c6e3

return types.FeeToken{}, sdkerrors.Wrapf(types.ErrInvalidFeeToken, "%s", denom)

Essentially, wasmd generates a tx with a random fee:
https://github.com/osmosis-labs/wasmd/blob/0f2794c47af3c1993f94c9f45953b3de6f4e2bf5/x/wasm/simulation/operations.go#L154

I think the solution should be to modify wasmd side and hardcode the denom to be "stake"

[p0mvn]

Seems that we only allow fees in "uosmo" in our simulator too:

osmosis/simulation/simtypes/legacy.go

Lines 38 to 39 in 1d9c6e3

	// Only allow fees in "uosmo"
	coins = sdk.NewCoins(sdk.NewCoin("uosmo", coins.AmountOf("uosmo")))

So I'm going to go ahead and make the change wasmd side and retag

[faddat]

Recommend v0.29.0 in fact.

Also, I just vendored x/wasm and x/globalfees into eve, and I gotta say it feels about right, there won't be as much upstream dependency chaos that way.

I'd be happy to hack on any of that for osmo.

[p0mvn]

The simulator was failing because of this. I think the calculations above are making it flaky so this change is made to unblock v12. Once the TODO above is addressed, this should be as well

[p0mvn]

Recommend v0.29.0 in fact.

Also, I just vendored x/wasm and x/globalfees into eve, and I gotta say it feels about right, there won't be as much upstream dependency chaos that way.

I'd be happy to hack on any of that for osmo.

v0.29.0 is still an RC. Also, we really want to get v12 out, and this is one of the last missing pieces.

Since regular wasmd tag requires additional changes to be compatible with Osmosis, I think we will go with v0.28 for the sake of delivering v12. However, happy to upgrade to v0.29 as soon as stable release is out.

Also, I just vendored x/wasm and x/globalfees into eve, and I gotta say it feels about right

Do you mean added it directly into the repository? How are you planning to integrate improvements from upstream?