Multi-tenant navigation with PA placeholder content

[macfarlandian]

Description of the change

Completes the initial preparations to support multiple tenants. In the final analysis this wound up including:

• adds placeholder content for PA. This is the bare minimum required to let you navigate around to the expected pages, but there is neither copy nor data yet for the metrics so I just left them out for now.
• replaces the automatic redirect to ND with a check for a "locked" Tenant in the data store. If the lock is engaged, the homepage will redirect to that tenant's home page, and direct visits to any other tenants' paths will result in a Not Found page.
• Adds a basic homepage with links to the available tenants. This is only intended for use in local and staging environments, though it will technically also be in prod if you manage to visit the base Firebase URL.
• Adds a feature flag for granular tenant releases per environment. This will make intermediate prod releases safer because we can suppress the PA pages entirely even while they are available in staging. (Direct visits to the url of a disabled tenant also result in Page Not Found, so it should look the same to an end user as if the tenant didn't exist.)

I tested as much of this functionality as I could in Jest but supplemented it with some pretty thorough manual testing, by editing my hosts file to point the domains of interest at my local dev server. There should be no change in behavior for the existing ND prod domain, and the new staging domains also worked as expected. (I also tested this in staging a bit but that environment isn't necessarily up to date with this branch now.)

Type of change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Configuration change (adjusts configuration to achieve some end related to functionality, development, performance, or security)

Related issues

Closes #389, closes #391

Checklists

Development

These boxes should be checked by the submitter prior to merging:

• Manual testing against realistic data has been performed locally

Code review

These boxes should be checked by reviewers prior to merging:

• This pull request has a descriptive title and information useful to a reviewer
• This pull request has been moved out of a Draft state, has no "Work In Progress" label, and has assigned reviewers
• Potential security implications or infrastructural changes have been considered, if relevant

[coveralls]

Pull Request Test Coverage Report for Build 753224932

• 30 of 32 (93.75%) changed or added relevant lines in 9 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-12.7%) to 60.466%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
spotlight-client/src/DataStore/TenantStore.ts	5	6	83.33%
spotlight-client/src/PageHome/PageHome.tsx	6	7	85.71%

Totals
Change from base Build 745401377:	-12.7%
Covered Lines:	1125
Relevant Lines:	1829

---

💛 - Coveralls

[jovergaag]

I wasn't able to test it locally, but the testing looks thorough! I realized in reading this that I'm confused about the URL that users are using to access the app. Pls help :)

[jovergaag]

There isn't a case where an org like CSG can view multiple tenants? I guess in this case they would not have a ".gov" email address... Just wondering if there is ever a use case that we would want to allow multiple tenant users.

[jovergaag]

Actually, as I have read this more thoroughly it looks like the tenant is coming from the current location. I guess I'm unclear how this is deployed in prod and the DNS magic that is allowing us to put this behind a .nd.gov domain? Is this part of the agreement with ND?

[macfarlandian]

yeah it's a bit convoluted. We do not, as yet, actually have a spotlight.recidiviz.org domain configured for prod. For ND they did indeed configure their own DNS to point dashboard.docr.nd.gov at our prod Firebase environment, which has been fine because the whole site just defaults to ND as the only tenant. But now the expectation is that PA is going to do the same with something.pa.gov, and eventually if we get a few more states on the platform we are going to want spotlight.recidiviz.org to exist as well.

And then the additional staging subdomains just let us replicate those different experiences in the pre-release environment. (The default staging domain being spotlight-staging.recidiviz.org, which is where you can access all the tenants at once)

Does that make sense?

[jovergaag]

Yes it does, very helpful thanks!

[jovergaag]

Cool GibHub Actions linting error integration above!