Making start-docker Contract-Agnostic

[amessbee]

This is a twin of a PR in dapp-agoric-basics repo.

Goal of this PR is to (maybe partially) close #92. Currently running of agoriclocal chain and deploying and starting contract are intertwined in this dapp. This is somewhat unnatural as chain should not depend on the files of any specific contract - apart from the ones that designated essential for its running.
Further, running a chain independent of a specific contract will allow testing of multiple dapp simultaneously running and interacting with each other which may unlock several scenarios that a developer may want to test for.

As per discussion with @toliaqat, here is a plan:

• docker compose file should not mount the contract directory as a volume. Rather it should mount (ideally) a single script (run-chain.sh) that necessary tasks for running of chain independently.
• run-chain.sh should do just that - run the chain and nothing else!

yarn start:contract should handle most of the heavy work including:

• setup a dedicated workspace for the contract (ws-offer-up here)
• copy tools needed for building, i.e., Makefile
• copy scripts and tools needed for required for making install-bundle, submit-proposal, vote etc. calls.
• create contract bundles on host machine, and then copy them to the workspace in docker container.
• copy all relevant files to workspace directory on the container.
• make build-proposal, install-bundle, submit-proposal, vote etc. calls needed to deploy and run the contract using scripts as before.
• update relevant docs. In particular, add guides to install agoric and agd CLI.
• Update getting-started docs if needed.

Link to IBIS document.

[usmanmani1122]

Suggestion:
Instead of running a container within a container (which further reduces the resources available to the child container), why don't we run two parallel docker containers and use a network bridge to communicate between them?

[toliaqat]

Why is there code related to codespaces here? That should be in a different PR to make sure that we have a shorter PR to review here.

[amessbee]

Asking users to install agoric and agd CLI to interact with getting-started seems like a big ask therefore we are moving towards the easier solution of running these commands inside the docker container ATM. T
here is little to no change needed in the docs.

[toliaqat]

I am removing myself from the review. I think @Jovonni or @mujahidkay are best suited to review and help make progress in this area.