Move all chain folders one layer deeper

[ValarDragon]

Currently we have a _non_cosmos top level folder.

I think we should put the cosmos chains in a single folder as well. I currently count 66 cosmos chains in the top level folder. This is too much for a top level folder imo, and it will only continue to increase. Having this many increases the UX hurdle of getting to the readme / getting a quick sense of what the repo is for.

[mccallofthewild]

I support this with the small amendment of cosmos -> chains

[pyramation]

I totally support this. We could add many utilities this way as well! e.g. some TS tooling to parse, lint, etc.

[JeremyParish69]

Some Thoughts:

• I think it makes sense to name the folder 'mainnets' to match the exists 'testnets' folder.
• I think Testnets should have it's own _IBC folder to not confuse testnet ibc connections with mainnet ibc connections. Therefore, I think it makes sense to also put the _IBC folder into the new ('mainnets'?) folder.
• I don't think with a mainnets folder, we don't need 'cosmos' folder. I think we're fine assuming that is the default, and just keeping _non-cosmos. If needed, I could see having a _non-cosmos folder under both mainnets and testnets, but I don't think we need to worry about that right away.
• We can create a new 'proposed' branch under the main repo to emulate what it would look like and allow dependent apps to test and validate on the new structure before merging to master.

[ValarDragon]

I support that @JeremyParish69 , thats a great idea