Closes issue #2357: Update status url to point to either dev or prod status service url

[HyperTHD]

Issue This PR Addresses

This PR closes #2357

Type of Change

• Bugfix: Change which fixes an issue
• New Feature: Change which adds functionality
• Documentation Update: Change which improves documentation
• UI: Change which improves UI

Description

The current status icon pointed to the production url for the status service. This is due to it being hard-coded. This PR addresses that by updating our docker config, next config, and the status icon's href to point to the correct status service url based on environment settings.

NOTE: This might not work immediately on the vercel views because they need to be updated as well. cc @humphd if this doesn't work off the bat.

Checklist

• Quality: This PR builds and passes our npm test and works locally
• Tests: This PR includes thorough tests or an explanation of why it does not
• Screenshots: This PR includes screenshots or GIFs of the changes made or an explanation of why it does not (if applicable)
• Documentation: This PR includes updated/added documentation to user exposed functionality or configuration variables are added/changed or an explanation of why it does not(if applicable)

[gitpod-io]

[humphd]

I was literally thinking about the need for this earlier today, and here you go and fix it! Awesome!

I need to add this URL to the Vercel env manually, which I'll do now.

[humphd]

Add STATUS_URL with value https://dev.api.telescope.cdot.systems/v1/status to Vercel Telescope config.

[HyperTHD]

Add STATUS_URL with value https://dev.api.telescope.cdot.systems/v1/status to Vercel Telescope config.

Would this file be the vercel.json file in the web folder? Confused about this

[humphd]

Sorry, "I added..." I have to do it manually, it's done.

[HyperTHD]

Apologizes for the late fix, vercel changes means this PR will probably have 1 failing test no matter what if I'm understanding this right

Changes were made

[humphd]

I'm not clear why Vercel keeps needing authorization for this STATUS_URL variable. I've tweeted them to ask if I'm doing it wrong (I did it the same as we usually do).

[humphd]

I thought @manekenpix said to remove this?

[HyperTHD]

I confused that with another declaration above, my mistake. Gonna clear this rn

[humphd]

Based on https://twitter.com/leeerob/status/1455553924119740421 I've disable git fork protection, so hopefully the next PR/push will not need Vercel authorization.