Make major release github workflow

[ValarDragon]

There are several steps that go into a major release, that can and should be automated, to lower complexity / overhead going into these releases!

• Run the existing binary creation tool Nicco made
• Make a PR to main, with a cosmovisor config, generated in tandem with the binaries from tool
  • Should be its own PR, as it may get denied for Fork upgrades
• Make a PR to main to update the import paths and go.mod for the new major release
  • Should also make a commit into every open PR to main to do the same find/replace. (Unless this will cause conflicts)
  • Do a PR if that commit has conflicts
• (Eventually) Make a PR that adds a version handler for the next upgrade
  • Add v10 upgrade boilerplate #1649
• Update chain JSON schema's recommended versions

[ValarDragon]

I believe this is obsoleted