Improve PostgreSQL and minio container builds

[samdoran]

Description

Make the UID and GID of the postgres user in the container match those of the current user. This makes the PostgreSQL data files easy to manage from the container host. Build a PostgreSQL image with the correct UID, GID, and our entry point script baked in. The fewer bind mounts the better.

Use environment variables to configure the UID and GID of the minio container. There is an entry point script that sets up the user account, so we don't need to maintain a separate container file.

Move container files into dev/containers . This keeps the repo root clean and makes builds easier.

Testing

1. Checkout Branch
2. Delete containers and local data

make docker-down
make delete-db
make delete-trino
make delete-trino-data
rm -rf pg_data/*
rm -rf .trino/parquet_data/.minio.sys

3. Start it all back up: make docker-up-min
4. Check that things came up ok make docker-logs
5. Load some data make load-test-customer-data

Notes

I would like to move all the dev container related files and data to dev/containers.

[codecov]

Codecov Report

Merging #4696 (6ab5646) into main (370e590) will increase coverage by 0.0%.
The diff coverage is n/a.

❗ Current head 6ab5646 differs from pull request most recent head f3ac753. Consider uploading reports for the commit f3ac753 to get more accurate results

@@          Coverage Diff          @@
##            main   #4696   +/-   ##
=====================================
  Coverage   93.8%   93.8%           
=====================================
  Files        367     367           
  Lines      30275   30229   -46     
  Branches    3580    3575    -5     
=====================================
- Hits       28383   28351   -32     
+ Misses      1226    1219    -7     
+ Partials     666     659    -7     

[samdoran]

One other thing I would like to do is unify the service and container names. All containers would have a koku- prefix and use dashes instead of underscores. Service names would not have the koku- prefix. This is a bit disruptive because it requires updating any values in the .env file locally.

Here is what the containers look like currently:

trino
hive-metastore
koku-koku-worker-1
koku_server
masu_server
koku-koku-base-1
koku-koku-create-parquet-bucket-1
kokuminio
koku_redis
koku-unleash
koku_db

This is what I would like to change them to:

koku-trino
koku-hive-metastore
koku-worker-1
koku-masu-server
koku-server
koku-create-parquet-bucket
koku-base
koku-minio
koku-redis
koku-unleash
koku-db

I can do that in a separate PR if it's less disruptive.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
1 Code Smell

No Coverage information
0.0% Duplication