feat(Global Environments): Introduce a new top level file type called global environments.

[gatzjames]

Highlights:

• Adds a new workspace type environment
• Collections can now use Global environments alongside collection environments
• Global environments can be synced using Cloud Sync / Git Sync
• Global environments apply on top of Base environments using the same hierarchy model

Next steps:

• Enable globals API in pre-request/after-response scripts
• Test Import/Export and make sure imports with globals work as expected
• Environment Settings
• Review the objects that need to be created for envs (e.g. filter out CookieJar or other stuff that don't make sense)

New Environment picker UI:

Global Environments in the Project view:

Updates to Models

• Workspace now has a new type environment
• A workspace can have an active Global Environment (workspaceMeta has a new property activeGlobalEnvironmentId that references that)

[jackkav]

can you include some screen shots in the description please. I think the ux is a bit contentious. I would also like to see a clear the environment model addressing the current inconsistencies in order to code review this approach.

[ihexxa]

Went through some parts like data model, rendering and the UI part is not checked yet.

[ihexxa]

nit: Should it be --color-font or color-bg?

[gatzjames]

Yep it's correct we want the color-font for bg here. Agree that it's counter intuitive but there are cases were we need the font color as bg 🫣

[ihexxa]

Tend to move forward but there are many details in the component so it may deserve more detailed check.

[ihexxa]

LGTM we've discuss several topics like relationship syncing, ux consistency and overall it looks to me. We will also apply it to the scripting feature, have more tests on it and move to the importing/exporting implementation.