Add capability to select different content servers for testing

[PhotoNomad0]

QA needs the ability to test code against QA or production servers.

• one possible approach would be to be able to select via the URL. For example we could add the server to the URL when starting the app (e.g. https://gateway-edit.netlify.app/?server=qa).

Indication will be given if the server is qa.
The server setting will persist until a new server is set via the url.
If the server is set to anything other than 'qa' the server will be set to production.

DoD:

QA can test against both QA and prod servers.

Details:

Per @mannycolon this may be handled using https://nextjs.org/docs/routing/dynamic-routes

[PhotoNomad0]

@elsylambert - working in 1.0.0 build 52f384b

to switch to QA server run with https://develop--gateway-edit.netlify.app/?server=QA, and then the app will use QA server until you do run with https://develop--gateway-edit.netlify.app/?server=PROD

When QA server is selected, there will be an indicator on app footer:

[elsylambert]

v1.0.0 build 52f384b QA

• Unable to access Organization using Account settings page. The app shows Network error and asks to login again. If you click Cancel on the modal, the Account setting page stays but the Organization dropdown does not work.

Steps:

1. Login to app using qa server url https://develop--gateway-edit.netlify.app/?server=QA.
2. It opened to previously opened project page.
3. Go to accounts settings page, Note: You can see the network error thrown that you are not logged iin.
   a. Cancel the modal. You stay on the Account settings but cannot select the organization. Select the language and Click Save and Continue. It opens the project page as in step2.
   b. Click Login on the error modal. It takes you back to login page. Enter your credentials and continue. Note that you are back to Account Settings page with the Network Error.
   

If you clear cache and login still see the network error but not the Project page (Step 2 ad 3.a.)

[PhotoNomad0]

@elsylambert I can reproduce the issue, investigating

[PhotoNomad0]

This issue appears to be that the app is still using the production server to get the org list.

[PhotoNomad0]

@elsylambert Fix is in v1.0.0 build 3c9167c

[elsylambert]

Verified in v1.0.0 build 1c04778. Able to test the develop build on QA server and on Prod server using the parametrized URL. works as expected.