ci: enable wasm lint/build/test on every PR and push to main.

[DimitrisJim]

Description

not running these could lead to subtle errors passing through with changes to ibc-go. Since we consume ibc-go as a library, it is a good idea to run these tests whenever it changes.

closes: #XXXX

Commit Message / Changelog Entry

ci: enable wasm lint/build/test on every PR and push to main.

see the guidelines for commit messages. (view raw markdown for examples)

---

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

• Targeted PR against the correct branch (see CONTRIBUTING.md).
• Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
• Code follows the module structure standards and Go style guide.
• Wrote unit and integration tests.
• Updated relevant documentation (docs/) or specification (x/<module>/spec/).
• Added relevant godoc comments.
• Provide a commit message to be used for the changelog entry in the PR description for review.
• Re-reviewed Files changed in the Github PR explorer.
• Review Codecov Report in the comment section below once CI passes.

[DimitrisJim]

wasm tests should still fail for time being.

[crodriguezvega]

💯

[damiannolan]

I think we originally had this under stricter rules because the contract tests did not have the mock vm yet.

Thanks @DimitrisJim 👍🏻

[chatton]

LGTM, left once comment about (possibly) a redundant test run

[chatton]

do we need to run them again on merge to main? The code on the PR should already be synced with main when they're running on the PR right?

[DimitrisJim]

yea should be redundant, can't think of a case where it wouldn't (maybe auto merge?).

Looking at our other workflows (callbacks and main ibc-go one), we do run em in so I'll just push this with it for now and we can drop em all at some point.