Change proto service for Balancer Msg (osmosis-labs#1469)

Closes: [osmosis-labs#1185](osmosis-labs#1185)

With proto Msg service defined twice(both in Balancer proto and gamm package proto), this is currently causing problems in typescript proto generation.

As @ValarDragon mentioned in osmosis-labs#1208,
> They existed at the same import path, because due to interface serialization
depending on the amino route (which depended on the proto import path),
changing the import path requires a state migration thats a bit cumbersome to
do.

This PR solves this by making txs under the correct package, but leaving balacner pool proto definition under the legacy wrong one, `package osmosis.gamm.v1beta1`. Solving the problem this way allows us to solve without having to need state breaking changes or additional migration for existing pools.

In addition to solving the exisitng problem of duplicated Msg in one package, this PR also changes stableswap pool proto package to the correct package.

- Change proto package for balancer msg

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

Merge pull request osmosis-labs#1481 from osmosis-labs/mattverse/gov-…

…unpool

v8 Emergency proposals upgrade

Update whitelisted pool IDs (osmosis-labs#1486)

Set upgrade hegiht

Apply suggestions from code review

Co-authored-by: Joe Abbey <[email protected]>

chore: v7.3.0 changelog (osmosis-labs#1397)

* fix changelog

* fix link

update changelog

chore: upgrade sdk to v0.45.0x-osmo-v7.7 (osmosis-labs#1241)

* chore: upgrade sdk to v0.45.0x-osmo-v7.7

* changelog

* changelog - v7.2.0

call EpochEnd event before increasing (osmosis-labs#1043) (osmosis-la…

…bs#1111)

(cherry picked from commit fb9cb2e)

Co-authored-by: Adam Tucker <[email protected]>

update changelog for v7.0.4 (osmosis-labs#1067)