feat: add base services compose file

[walkah]

Summary

This PR simplifies local development by gathering all of the supported (3rd party) services in a single docker compose file (docker/docker-compose.base.yml):

• adds ./stack compose-services to run base services (still use ./stack compose-init to initialize the chain data)
• removes ./stack commands for chain, ipfs, bacalhau
• updates docker-compose.dev.yml to include docker-compose.base.yml
• adds postgres to the stack (for upcoming solver work)
• updates LOCAL_DEVELOPMENT.md with modified instructions

[walkah]

@cla-bot check

[cla-bot]

The cla-bot has been summoned, and re-checked this pull request!

[bgins]

When running compose-init a second time after running the base services, the following error is reported:

Error response from daemon: remove lilypad_chain-data: volume is in use - [440d450180a1295ee4d50c1f79e37f565d761cc59e9ff2de5f1f2b3e522c5685]

Everything runs fine starting the base services a second time without running compose-init a second time, but should this command give us a clean slate? (Not necessary on the PR, this does what we need for this PR.)

[bgins]

Tested it out, works well! ✨

Left a couple questions and have one more. Should compose-up be updated to run compose-services? Or maybe update the "Using Docker Compose" section in LOCAL_DEVELOPMENT to request users run compose-services?

[bgins]

Tested it out, works well! ✨

Left a couple questions and have one more. Should compose-up be updated to run compose-services? Or maybe update the "Using Docker Compose" section in LOCAL_DEVELOPMENT to request users run compose-services?

Ah I see what I was missing. We include the base services here:

lilypad/docker/docker-compose.dev.yml

Lines 2 to 3 in 1558133

	include:
	- docker/docker-compose.base.yml