feat: settings HTML tabs

[rrama]

Description

Settings laid out in tabs. AI generated with some guidance, so probably removed something we cared about..

Checklist

• Tests added and all succeed
• N/A
• Regenerated mocks, etc. (make generate)
• N/A (We should make the example page be generated though)
• Linted (make lint-fix)
• README.md updated, if user-facing
• N/A
• License file updated, if new 3rd-party dependency is introduced
• N/A

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[rrama]

Dammit AI, why put 2022 here...

[snyk-pr-review-bot]

PR Reviewer Guide 🔍

🧪 PR contains tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Broken Selector for Reset Badges 🟠 [major] The function updateSourceBadgesForReset now attempts to find a container with ID folder- + index + -advanced. However, looking at the generated HTML in scripts/config-dialog/config_output_single_solution.html and the tab implementation, folder settings panes are actually assigned IDs like folder-pane- + index. This mismatch causes the selector to fail, meaning users will not see the "Will Reset" visual feedback when clicking the reset button for folder overrides. var container = dom.get("folder-" + folderIndex + "-advanced"); Inconsistent Folder Naming 🟡 [minor] The loop in GetConfigHtml matches folders by comparing f.Path() == fc.FolderPath. If the workspace provides relative paths or different URI schemes than what is stored in StoredFolderConfigs, the matching will fail and labels will fall back to filepath.Base. Since the logic elsewhere in the system (e.g. UpdateSettings in configuration.go) uses types.PathKey for map keys, applying normalization here would ensure consistent folder labels in complex workspaces. if f.Path() == fc.FolderPath {

📚 Repository Context Analyzed This review considered 76 relevant code sections from 12 files (average relevance: 0.96) scripts/config-dialog/main.go (lines 1-69) application/server/configuration.go (2 segments, lines 188-390) application/di/test_init.go (lines 1-117) domain/ide/command/folder_handler.go (lines 1-199) application/config/config.go (lines 1-196) infrastructure/code/code_html.go (lines 1-148) infrastructure/iac/iac_html.go (lines 1-120) ... and 5 more file(s)