Consistently handle how/when changes in the TC GUI are persisted to file

[hhonisch]

Please describe feature/problem details and the solution you'd like.
As of now, when using the TC GUI, it's kind of confusing when changes in the TC GUI are persisted to file. As of now, it works like this if I'm not mistaken;

• Environment settings: Changes are persisted automatically, no explicit save is needed
• Collection and folder settings: Changes need to be saved explicitly, a "Save" button is available
• Request settings: Changes need to be save explicitly, but no "Save" button is available

Describe alternatives you've considered
Please handle this in a consistent manner. Personally, I'd perfer that in all cases, an "explicit save" was required to persist TC GUI changes to file. Also it would be nice that when trying to close a TC GUI tab in VSCode that has unsaved changes, VSCode would give me the usual "Do you want to save the changes?" dialog that it gives me for normal files.

Are you using the free version/paid version/trial:
Paid version

[rangav]

Thank you for the feedback, We will review it.