Remove Trino: Superset reads fuel-db directly as fuel_ro (PD-14)

trino/ deleted; the role trino_ro becomes fuel_ro, its password read from a
secret file at connect time; dashboards' SQL and column list for PostgreSQL;
the Compose project is renamed petrolyst, with volumes pinned to their old
names. AGENTS.md points to the architecture context. Not deployed: the next
deploy needs README's one-time steps first.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

petrolyst-insights/dashboards/README.md

@@ -11,11 +11,11 @@ image, so changes here do not rebuild or restart Superset.
 
   Build and import:
 
-      docker cp atoma/import_bundle.py fuel-monitoring-superset-1:/tmp/
-      docker exec fuel-monitoring-superset-1 /app/.venv/bin/python /tmp/import_bundle.py --show-database
+      docker cp atoma/import_bundle.py petrolyst-superset-1:/tmp/
+      docker exec petrolyst-superset-1 /app/.venv/bin/python /tmp/import_bundle.py --show-database
       python3 atoma/build_bundle.py --database-uuid <printed uuid> --out atoma-dashboards.zip
-      docker cp atoma-dashboards.zip fuel-monitoring-superset-1:/tmp/
-      docker exec fuel-monitoring-superset-1 /app/.venv/bin/python /tmp/import_bundle.py /tmp/atoma-dashboards.zip --user <username>
+      docker cp atoma-dashboards.zip petrolyst-superset-1:/tmp/
+      docker exec petrolyst-superset-1 /app/.venv/bin/python /tmp/import_bundle.py /tmp/atoma-dashboards.zip --user <username>
 
   Exit status 2 means a dataset's columns differ from its view: regenerate `atoma/columns.tsv`
   (command in its header), rebuild and import again.
@@ -34,12 +34,12 @@ image, so changes here do not rebuild or restart Superset.
 
       docker exec fmdb-scratch-superset /app/.venv/bin/python /tmp/import_bundle.py /tmp/atoma-dashboards.zip \
           --user admin --embedded-out /tmp/embedded-dashboards.json --embed-domain http://127.0.0.1:8098
-      docker cp fmdb-scratch-superset:/tmp/embedded-dashboards.json <Petrolist>/.local/fmdb-scratch/
+      docker cp fmdb-scratch-superset:/tmp/embedded-dashboards.json <Petrolyst>/.local/fmdb-scratch/
 
 Export from a running instance (inside the container, as the server's deploy user):
 
-    docker exec fuel-monitoring-superset-1 superset export-dashboards -f /tmp/dashboards.zip
-    docker cp fuel-monitoring-superset-1:/tmp/dashboards.zip .
+    docker exec petrolyst-superset-1 superset export-dashboards -f /tmp/dashboards.zip
+    docker cp petrolyst-superset-1:/tmp/dashboards.zip .
 
 Import is the reverse with `superset import-dashboards -p <zip> -u <username>`. The
 username must be an existing Superset user, which here means someone who has signed in