chore: update .vscode and gitlab ci for pipeline jobs

What does this MR do?

Fixes the .vscode/settings.json parser issue by removing unsupported JSON comments from the settings file. This ensures the compliance checker correctly detects the presence of the Ruff linter configured in the project's VS Code settings.

Motivation

Previously, the .vscode/settings.json contained comments which caused JSON parsing errors in the compliance checking code, leading to false negatives on Ruff detection. Removing comments corrects the JSON format, improving the accuracy and reliability of the compliance checks without changing functional behavior.

Scope of Changes

• Updated the .vscode/settings.json file in the repository to remove JSON comments.
• No code changes were made outside of the valid JSON format fix.
• This is a non-breaking internal change that improves the compliance reporting accuracy.

Risks and Mitigation

• Risk: Minimal; the change is only formatting the .vscode/settings.json file to valid JSON.
• Mitigation: The change was tested locally to verify check_vscode_settings_content now correctly detects Ruff presence.
• No impact on runtime behaviors or user workflows.

How to Test

1. Pull this branch and run the compliance checker locally.
2. Confirm the .vscode/settings.json file exists and is valid JSON (no comments).
3. Verify the compliance report shows:
   • ✅ .vscode/settings.json (file exists)
   • ✅ .vscode/settings.json have Ruff (Ruff detected)
4. Validate all existing unit tests still pass.

Checklist

• Code is more maintainable and easier to understand
• No functional or UI changes (only config cleanup)
• Existing tests pass
• Documentation is up to date (configuration docs reflect valid .vscode/settings.json)

Related Issues

• Fixes issue with Ruff detection false negatives due to invalid JSON in .vscode/settings.json.
• Related to recent compliance checker improvements and .vscode documentation updates.