Support for local and server profiles and actions

[worksofliam]

Introduce functionality to manage both local (in VS Code) and server profiles, enhancing the user experience by allowing seamless access to connection profiles. Profiles created in the IFS are shared across all users on that system. Created the JSON schema for profiles and updated related commands to accommodate these changes.

• Ability to store profiles in the connection, or inside /etc/.vscode/profiles.json in the IFS. Workspace profiles are not possible in this PR.
• Also added the same support for actions.json, which can also exist in /etc/.vscode/profiles.json as well as VS Code settings and workspace config.
• Button to reload the config files in the connection settings

How to test this PR (with actions)

1. Open up VS Code with a local workspace folder open
2. Create or open .vscode/actions.json locally and ensure the content assist works for the JSON schema
3. Create or open /etc/.vscode/actions.json on the IFS and ensure the content assist works for the JSON schema
4. Put valid actions in both files, and when executing a local action

Todo list as of May 7th 2025

1. Close this PR and create a new one
2. Use ConfigFile as the base
3. ConfigFile needs to also support VS Code configuration point (right now it only checks the server and the workspace, not the VS Code config)

Checklist

• have tested my change
• have created one or more test cases
• updated relevant documentation
• Remove any/all console.logs I added
• have added myself to the contributors' list in CONTRIBUTING.md

[github-actions]

👋 A new build is available for this PR based on 4a4579b.

• Download here.
• Read more about how to test

[SanjulaGanepola]

Noticed a couple issues when testing:

1. Only remote actions are showing when both local and remote actions are defined. Removing the remote actions allows the local ones to show. Is this expected?
   
2. Only remote profile shows up in the view:
   

[SanjulaGanepola]

Side note, just FYI this can be done with https://www.npmjs.com/package/jsonschema to just use the json schema we have defined. We do this for PE and it works pretty well.

[worksofliam]

This is something I will add later.

[worksofliam]

@SanjulaGanepola Please review again.

Only remote actions are showing when both local and remote actions are defined. Removing the remote actions allows the local ones to show. Is this expected?

No. This was a bug and is now solved.

Only remote profile shows up in the view:

Yes, this is valid for the time being. We are not going to allow profiles to be defined as part of the local workspace (this we have the .env library list control)

[worksofliam]

Drafting this to work on the bigger PR.