Add PGAdmin & SubQuery Node Hot-Reload

[jorgecuesta]

This pull request introduces significant improvements to the local development environment and security practices:

Enhanced Local Development:

• PGAdmin Integration: Introduced PGAdmin for easier database management through Docker Compose.
• Hot Reloading: Added nodemon for automatic code reloading during development, reducing manual restarts.
• Simplified Scripts and Docker Configuration: Streamlined scripts in package.json and optimized Docker Compose configuration for better developer experience.
• Clearer Local Dev Instructions: Updated Localdev.run.xml with guidance for running the project in IntelliJ IDEs.

Strengthened Security:

• Removed Environment Files: Eliminated .env files for environment variables, enhancing security by storing them outside the codebase.
• Environment Variable Configuration: Updated Dockerfiles to use environment variables for configuration, improving maintainability and security.
• Production Hot-Reload Warning: Added a warning message in the node-entrypoint.sh script if hot-reload is enabled in a production environment.

Additional Improvements:

• Updated cosmjs submodule.
• Added comments for future Dockerfile enhancements.
• Clarified changes to --workers= in docker-compose.yml.
• Refactored Docker files and scripts for better maintainability.

These changes streamline the development workflow, improve project security, and lay the groundwork for further enhancements.

[jorgecuesta]

Btw here are few reasons to use docker compose instead of docker-compose:

• Simplicity: If Docker Compose features are integrated into the Docker CLI, you don’t need to install two separate tools anymore. You just need one (docker) and can run all commands from it.

• Eases Distribution: Docker is universally recognized, so having Compose as a part of the main Docker CLI ensures that the Compose specification can be readily available wherever Docker is.

• Better Integration: Compose is part of the Docker CLI now, as 'docker compose', which means it will have top-level integration and will likely get new features and improvements quicker than docker-compose.

• Compatibility: Generally, all of your existing docker-compose command line flags and functionality should still work with docker compose, ensuring backward compatibility.

[jorgecuesta]

@bryanchriswhite Based on our talks I pushed a major change to this PR, please if you have time give it a try before approving.

[bryanchriswhite]

I'm having trouble building the composition. I get the same error whether I use yarn run docker:build or yarn run docker:build:no-cache:

[jorgecuesta]

I'm having trouble building the composition. I get the same error whether I use yarn run docker:build or yarn run docker:build:no-cache:

base on the logs, look like you forget to create the .env copy from the .env.sample, btw, the old .env & .env.develop are not needed anymore