feat: development environment using gitpod

[faddat]

Description

Closes: #11817

This PR adds a .gitpod.yml file that uses ghcr.io/faddat/cosmos, an image built to allow the use of any aspect of cosmos. This way, in order to begin working with the sdk, users don't even need to set up a local development environment.

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• included the correct type prefix in the PR title
• added ! to the type prefix if API or client breaking change
• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• followed the guidelines for building modules
• included the necessary unit and integration tests
• added a changelog entry to CHANGELOG.md
• included comments for documenting Go code
• updated the relevant documentation or specification
• reviewed "Files changed" and left comments if necessary
• confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed the correct type prefix in the PR title
• confirmed ! in the type prefix if API or client breaking change
• confirmed all author checklist items have been addressed
• reviewed state machine logic
• reviewed API design and naming
• reviewed documentation is accurate
• reviewed tests and test coverage
• manually tested (if applicable)

[alexanderbez]

I don't know what gitpod is, nor have I ever used it, so I don't really feel comfortable approving. Maybe someone with experience with this can chime in.

[faddat]

Totally fair, let me walk ya through:

Gitpod is a browser extension + cloud based container-runner with vscode in it.

The effect?

When you visit a github repository (any even without the .gitpod.yml) you can click the green gitpod button and it checks out the code for you.

When you do have the .gitpod.yml file, it even knows where to run the code.

So in this case that file is a full cosmos-sdk development enviornment.

It runs that as your shell and gives you:

I think it would be helpful for onboarding.

Users still push to their own repository, it just gets them checked out and going more quickly.

[tac0turtle]

can you link to this image? what does it contain?

[faddat]

yes, the image is automatically built every hour here and I want to merge it into the cosmos-sdk-- the entire build system for it

https://github.com/faddat/archlinux-docker

The cosmos folder builds that image.

[faddat]

if we merge:

#11768

Then that development environment image would be built here, hourly.

It links to an external repository only because well, to put it softly, our docker situation -- and the build situation that comes from using Dockerfiles that are muslc-based and ancient, aren't so great.

[amaury1093]

Let's not use external dependencies. If #11768 is a dependency, let's put this PR as draft for now, and open it again when the dep is merged.

[faddat]

kk

[alexanderbez]

I don't understand why anyone would use this TBH. I'm okay with adding a simple config file though.

[faddat]

it's my primary development environment

[faddat]

Hey, so if you want to see this in action, you'd install the gitpod browser extension, and then open up the Juno or osmosis repository.

All the tooling is there, and stuff "just works"

That is the goal of the change overall.

[tac0turtle]

Hey, im fine with merging this, I think the missing part for me is to figure out what all the docker image is doing.

[tac0turtle]

Ill close this for now, lets get the docker image updated then we can reopen this