Semi-automated tooling to create PRs for unlisted denoms

[joe-bowman]

Summary

Related to #1635

Whenever a new denom is present on Quicksilver, that needs to be routed back it's host zone prior to sending to osmosis or elsewhere, it must be added to the chain registry under the quicksilver-2 zone, for the Skip API to present an appropriate route.

Similarly, new qAssets must also be listed in the same way.

Additionally, for a denom (rewards or qAsset) to be shown on Mintscan, it must be listed in the Mintscan repository.

Finally, for an asset to be listed on the Osmosis frontend (qAssets only), an entry must be made on the assetlists repo.

Tooling ought to be able to parse the current main branch of these repositories, compare vs QS API endpoints (supply and ibc denom trace will likely be useful here), and determine the correct diff with which to create a PR to add the assets in the appropriate place.

Resources

https://github.com/cosmos/chain-registry
https://github.com/cosmostation/chainlist
https://github.com/osmosis-labs/assetlists

[joe-bowman]

Ajaz suggested potentially using some AI here to assist with the PR process.