Yo, does anyone know why EDR tries to install everything again from scratch i.e.

2024-07-12 12:58:48 — INFO — Running with edr=0.15.1

2024-07-12 12:58:48 — INFO — Installing packages for edr internal dbt package...

2024-07-12 12:58:48 — INFO — Running dbt --log-format json deps --project-dir /usr/local/lib/python3.8/dist-packages/elementary/monitor/dbt_project

2024-07-12 12:58:52 — INFO — Running with dbt=1.8.0

2024-07-12 12:58:52 — INFO — Updating lock file in file path: /usr/local/lib/python3.8/dist-packages/elementary/monitor/dbt_project/package-lock.yml

2024-07-12 12:58:52 — INFO — Installing dbt-labs/dbt_utils

2024-07-12 12:58:52 — INFO — Installed from version 0.8.6

2024-07-12 12:58:52 — INFO — Updated version available: 1.2.0

2024-07-12 12:58:52 — INFO — Installing elementary-data/elementary

2024-07-12 12:58:52 — INFO — Installed from version 0.15.1

2024-07-12 12:58:52 — INFO — Updated version available: 0.15.2

2024-07-12 12:58:52 — INFO —

2024-07-12 12:58:52 — INFO — Updates available for packages: ['dbt-labs/dbt_utils', 'elementary-data/elementary']

When I already have everything it needs installed???

EDR under the hood is implemented as separate DBT project. That DBT project is in EDR pipy packages, but its dependencies are not in the package. So it installs it which means that VENV directory (if you use VENV) should be writeable