Modernize development environment setup

  This overhaul simplifies and unifies the local and devcontainer development
  experience with consistent tooling and clearer documentation.

  Key changes:

  Scripts (verb-first naming convention):
  - cc-containers: Manage Docker containers with profiles (dev, s3, full)
  - cc-db-env: Set DB_CONNECTION_STRING and CLOUD_CONTROLLER_NG_CONFIG
    Usage: eval "$(cc-db-env psql ccdb)" or eval "$(cc-db-env mysql test)"
  - cc-generate-config: Generate cloud_controller.yml with optional custom name
    Modes: local-temp-storage, local, storage-cli
  - cc-reset-db: Drop and recreate all databases
  - cc-setup-devcontainer: One-time setup for devcontainer/codespaces
  - cc-setup-ide: Copy IDE configs (VS Code, IntelliJ)
  - cc-install-storage-cli: Install storage-cli for S3 blobstore testing

  Docker Compose:
  - Add profiles: dev, s3, broker, diego, full
  - Add SeaweedFS for S3-compatible blobstore testing (local only)
  - Separate nginx configs for local vs devcontainer (different upstreams)
  - Use docker-outside-of-docker feature for devcontainer
  - Consistent COMPOSE_PROJECT_NAME to avoid container conflicts

  Configuration:
  - Generated configs use 127.0.0.1.nip.io (vcap.me no longer resolves)
  - Support local-temp-storage, local, and storage-cli blobstore modes
  - Custom config names for running multiple CC instances

  IDE configs:
  - Update IntelliJ run configs with STORAGE_CLI_PATH
  - Rename Mariadb configs to Mysql
  - Add VS Code extensions.json
  - Auto-copy run configs in devcontainer

  Documentation:
  - Rewrite README with quick start for both devcontainer and local
  - Document all helper scripts and environment variables
  - Keep detailed test configuration docs (DB_CONNECTION_STRING, etc.)
  - Add brew database option and ports reference

  Removes: devenv.sh, codespaces_*.sh, setupDevelopmentEnvironment.sh

Author: johha