feat: Create .gitpod.yml

[faddat]

Description

Yesterday I made some changes to the standard dev env that we're using and to my surprise, they "just worked". That includes adding docker to the image so that we could do protocol buffer builds. It also has all the rocksdb tooling installed in the filesystem for those with container allergies.

Caveat: the rocksdb installed here is of the v7 variety. We would want to update our rocks library to grocksdb.

Nonetheless, this tooling represents a step forward. By clicking a little green button, developers can work on the sdk in a known-good environment.

image: ghcr.io/notional-labs/cosmos

That image is built here daily using cron via github actions and each build is observable.

https://github.com/notional-labs/containers/blob/master/cosmos/Dockerfile

• feat: Build own docker image and use ghcr #11768 is really just an attempt to build these images here, and contains most of the code found at:

• https://github.com/notional-labs/containers/

[julienrbrt]

I think we didn't want to use an external docker image.

@marbar3778 cannot we just fork notional's container repository and use the image built for this gitpod config? It has the advantage to not add it on this repository like #11768 would do.

[faddat]

Works for me.

Just need a fork repo and then happy to maintain it from there.

Per #11768 -- I figure we've two choices:

• move "all the things" here (I kind of like this approach. might streamline things some)
• make a repo where we move the cosmos docker image build tooling.

[faddat]

This is getting relevant again, as is #11768

[tac0turtle]

since this is only gitpod specific