Change the dir we read config files from.

[rsalmond]

This changes our config loading logic to fetch files from /config instead of a path relative to the source code.

We need this because the way kubernetes injects config files completely hides all the files in the target directory. Which is to say, if we inject our config files to /app, we hide all our source code and assets.

By fetching config from a separate root dir, we don't have this problem.

It seems to still work okay with the local dev experience as well, but would love to get a confirmation.

$ k logs backend-7854c7945f-czd8j

Attention:
Turborepo now collects completely anonymous telemetry regarding usage.
This information is used to shape the Turborepo roadmap and prioritize features.
You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
https://turborepo.com/docs/telemetry

turbo 2.5.6

(node:1) ExperimentalWarning: Support for loading ES Module in require() is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
{
  POSTGRES_USER: { value: 'grassroots', source: '/config/.env.production' },
  POSTGRES_PASSWORD: { source: '/config/.env.production' },
  POSTGRES_HOST: { value: 'grassroots-rw', source: '/config/.env.production' },
  POSTGRES_DATABASE: { value: 'grassroots', source: '/config/.env.production' },
  POSTGRES_PORT: { value: '5432', source: '/config/.env.production' },
  VITE_BACKEND_HOST: {
    value: 'https://grassroots.gpotoolsstage.ca/api',
    source: '/config/.env.production'
  },
  VITE_FRONTEND_HOST: {
    value: 'https://grassroots.gpotoolsstage.ca',
    source: '/config/.env.production'
  },
  GOOGLE_AUTH_CALLBACK_URL: {
    value: 'http://grassroots.gpotoolsstage.ca/api/auth/google/callback',
    source: '/config/.env.production'
  }
}

[tdresser]

CI failures look real: like ci isn't seeing the db config maybe?

I'll test locally on Monday.