Non-intuitive docker setup due to config file override

[sergei1152]

Describe the bug I was just setting up the project via podman/ docker.

I noticed that once I setup the volume mount for the config, my environment variable changes had no effect to the application.

This is because by default, the application prefers the config file over any environment variables: https://github.com/reaper47/recipya/blob/main/internal/app/app.go#L336

This isn't intuitive (at least for me). It would make more sense if the config file lived in a non-persistent volume store, however the app recommends mounting it when initializing the docker container.

Alternatively, the app can make env vars override config file (and update them).

Expected behavior If i re-recreate the docker container but with different environment variables, it should reflect the new state of app.

Currently it does not because the config.json is saved in the same volume as the rest of the application data.

Thanks for building the project! This seems great and looking forward to helping me track my recipes with it :)