Read environment variables from .env file during development

[surchs]

In development, it's pretty involved to always export a local .env file to the local shell in order to test setting changes. It can also lead to strange behaviour when I forget that I had already set a variable in my shell, but then change the .env file without re-exporting it.

We should find a way for the local .env file to be automatically read by the development server so that I can

• make a change to a ENV variable in the .env file
• not export the .env file
• see the change in the .env file applied to the behaviour of the app after a relaunch (ideally automatic relaunch from vite dev-mode)

[github-actions]

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 75 days.
We have applied the _flag:stale label to indicate that this issue should be reviewed again.
When you review, please reread the spec and then apply one of these three options:

• prioritize: apply the flag:schedule label to suggest moving this issue into the backlog now
• close: if the issue is no longer relevant, explain why (give others a chance to reply) and then close.
• archive: sometimes an issue has important information or ideas but we won't work on it soon. In this case
  apply the someday label to show that this won't be prioritized. The stalebot will ignore issues with this
  label in the future. Use sparingly!