Allow Hydra service to be configurable / run on separate infrastructure

[batpad]

Relates to #206

Based on conversation with @kamicut (@kamicut please feel free to correct things I might have gotten wrong) -

Currently, OSM Hydra, that handles OAuth for the osm-teams application, runs as a separate docker container, but needs to be run on the same machine / infrastructure as the osm-teams NextJS application. This has a few disadvantages:

• It limits the hosting options for osm-teams as the host would need to support running docker-compose and that means one can't use Vercel or other NextJS specific hosting platforms.
• It makes the OSM Hydra architecture very coupled to osm-teams. In the current architecture, it's impossible to look at possibly replacing OSM Hydra with a SaaS product like Auth0, so that we need to maintain less infrastructure.
• In general, being able to decouple the osm-teams web applicaton and the OSM Hydra auth service seems like sensible, flexible architecture going forward.

How I roughly understand what needs to be done (@kamicut you will need to fill in specifics of the way forward in more detail / where more investigation needs to happen):

• The osm-teams container / application should accept environment variables to define the IP / port of the OSM Hydra service - if possible, allow passing of env vars to a generic auth service like Auth0.
• We need to ensure that OSM Hydra and OSM Teams are able to communicate over the public internet / with a public IP don't require to be in the same subnet or so.

This does seem like there's a few unknowns here that would be good to lockdown.

@kamicut @vgeorge - am going to put this into the Refactor milestone for now, but, I think this should not change the setup of the core app very much, and we could perhaps move to take on later, but let's discuss.

[batpad]

From chat:

Ory has released a “cloud offering” https://www.ory.sh/, this could help us solve the hydra hosting solution. - @kamicut

[kamicut]

We've currently done this by running the osm-teams repository auth-v1 branch as a a separate application. We've also created some tentative work in https://github.com/developmentseed/osm-teams-auth that could replace the auth-v1 branch.