Create CI Tooling for managing Osmosis Packages

[mattverse]

Background

Right now we have a pain point upon having any updates on Osmosis packages (e.g osmomath, osmoutils, ibc-hooks etc), e2e testing would be failing since we have to update go.mod to correctly use the updated commit for package.

As of right now, we manually have to run go get <package_name> <branchname> to correctly update the dependencies.

Suggested Design

Create a bot or a CI tooling that handles this extra overhead of having to manually update go mod dependency of the branch.
If tagged, the bot can run the go get command and make an extra commit on the branch to properly use the right commit in go.mod for the package.

Acceptance Criteria

• We have implemented a tooling for automating dependency commit hash update
• Test run has successfully succeeded

(Extra points)
Find a workaround for golang/go#32955

[pysel]

hey @mattverse , I think we had a similar issue to this: #4266. Should we close this?