refactor: new dev/prod containers

- Use a single Dockerfile for all Zeppelin services
- Add a Dockerfile in project root that can be used by
  app hosting services
- Provide a standalone and lightweight prod setup
  - Standalone is the same as the old setup, with mysql+nginx
  - Lightweight only runs bot+backend+dash, no mysql/nginx
- Remove mounted mysql data folders for dev and prod
  - This resolves permission issues caused by the mount
  - The mysql service uses a regular named volume now
- Simplify .env options and clearly separate different prod setups
- Remove update.sh
  - Different setups require different update procedures, so a common
    update.sh no longer works

docker/development/nginx/default.conf

@@ -3,24 +3,22 @@ server {
   listen [::]:443 ssl http2;
   server_name localhost;
 
-  root /zeppelin/dashboard/dist;
+  # Using a variable here stops nginx from crashing if the dev container is restarted or becomes otherwise unavailable
+  set $backend_upstream "http://devenv:3001";
+  set $dashboard_upstream "http://devenv:3002";
 
   location / {
-    index index.html;
-    try_files $uri $uri/ /index.html;
+    # Using a variable in proxy_pass also requires resolver to be set.
+    # This is the address of the internal docker compose DNS server.
+    resolver 127.0.0.11;
+    proxy_pass $dashboard_upstream$uri$is_args$args;
   }
 
-  # Using a variable here stops nginx from crashing if the dev container is restarted or becomes otherwise unavailable
-  set $backend_upstream "http://devenv:_API_PORT_";
-
   location /api {
     # Remove /api/ from the beginning when passing the path to the API process
     rewrite /api(/.*)$ $1 break;
 
-    # Using a variable in proxy_pass also requires resolver to be set.
-    # This is the address of the internal docker compose DNS server.
     resolver 127.0.0.11;
-
     proxy_pass $backend_upstream$uri$is_args$args;
     proxy_redirect off;