Create test to ensure environment variables are read in correctly

[surchs]

We need a test to ensure NB_API_QUERY_URL and NB_IS_FEDERATION_API env vars are correctly parsed, checked, and if needed adjusted for the app:

query-tool/src/utils/constants.ts

Lines 2 to 14 in 99fc5c0

	export const queryURL: string = baseAPIURL.endsWith('/')
	? `${baseAPIURL}query/?`
	: `${baseAPIURL}/query/?`;
	export const attributesURL: string = baseAPIURL.endsWith('/')
	? `${baseAPIURL}attributes/`
	: `${baseAPIURL}/attributes/`;
	export const nodesURL: string = baseAPIURL.endsWith('/')
	? `${baseAPIURL}nodes/`
	: `${baseAPIURL}/nodes/`;
	export const isFederationAPI: string =
	import.meta.env.NB_IS_FEDERATION_API === undefined ? true : import.meta.env.NB_IS_FEDERATION_API;

What needs to happen:

• write a cypress test (e2e probably) that mocks the ENV file / ENV variables
• confirm that these variables are read in as expected, e.g. by confirming the axios call goes out to the right API (cy.intercept)

[github-actions]

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 75 days.
We have applied the _flag:stale label to indicate that this issue should be reviewed again.
When you review, please reread the spec and then apply one of these three options:

• prioritize: apply the flag:schedule label to suggest moving this issue into the backlog now
• close: if the issue is no longer relevant, explain why (give others a chance to reply) and then close.
• archive: sometimes an issue has important information or ideas but we won't work on it soon. In this case
  apply the someday label to show that this won't be prioritized. The stalebot will ignore issues with this
  label in the future. Use sparingly!

[surchs]

@rmanaem wdyt about this one? transfer or close?

[rmanaem]

Let's transfer this.

[github-actions]

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 75 days.
We have applied the _flag:stale label to indicate that this issue should be reviewed again.
When you review, please reread the spec and then apply one of these three options:

• prioritize: apply the flag:schedule label to suggest moving this issue into the backlog now
• close: if the issue is no longer relevant, explain why (give others a chance to reply) and then close.
• archive: sometimes an issue has important information or ideas but we won't work on it soon. In this case
  apply the someday label to show that this won't be prioritized. The stalebot will ignore issues with this
  label in the future. Use sparingly!