feat(#303): Default Environment

[n00o]

Add environment to the presets tab which will set the default environment on opening a collection. Show default environment inside of environment selector. Also add cli support for default environments.

Description

This is to fix #303 by adding the property called environment inside of Collection > Presets. The collection descriptor file, bruno.json will now have the preset structure of:

{
  "presets": {
     "defaultUrl": "",
     "defaultRequestType": "",
     "environment": null
  }
}

The preset environment will only change the environment under these conditions:

• The collection is first being opened
• The collection is being opened again and the current session had the environment set to No Environment (if its something else then it won't set the environment)

In the future we can rely on something like lastEnvironment to override the preset environment if people set it in their preferences.

Default_Environment.mp4

The environment selector now has a helpful indicator showing what the preset environment is by the yellow (Default) value at the end of it. Any old collections that don't have a preset environment or the environment can't be found in the current list of environments will default to No Environment insuring that nothing breaks.

Some behavior that I need some guidance on @helloanoop, would be the formatting of (Default) indicator and whether to have it display next to No Environment if an environment preset is defined but not found. Currently I am setting it to No Environment in the environment selector and showing an error message on collection open when environment can't be found.

Now Bruno cli will try to look for the new environment preset value and set it as the environment if none is given.

I think this is a very helpful QOL change that will make opening and testing APIs a quick and easy process.

Contribution Checklist:

• The pull request only addresses one issue or adds one feature.
• The pull request does not introduce any breaking changes
• I have added screenshots or gifs to help explain the change if applicable.
• I have read the contribution guidelines.
• Create an issue and link to the pull request.

Note: Keeping the PR small and focused helps make it easier to review and merge. If you have multiple changes you want to make, please consider submitting them as separate pull requests.

Publishing to New Package Managers

Please see here for more information.

[Napam]

I personally would like something like this, is there any plans to incorporate such functionality? @helloanoop