fix: folder scope in Settings now correctly reads/writes folder-specific settings (fixes PlatformNetwork/bounty-challenge#21930)

[echobt]

Summary

Fixes PlatformNetwork/bounty-challenge#21930

The folder scope in Settings was not behaving as folder-only. When users selected a folder and modified settings, the changes were applied to user-level settings instead of folder-specific settings.

Changes

The folder scope fix (already on main via commit 521620d) ensures:

• SettingsDialog.tsx: All settings panels receive folderPath prop when folder scope is active
• SettingsEditor.tsx: SettingItem reads/writes folder-specific settings via getEffectiveSettingsForPath(), setFolderSetting(), and resetFolderSetting()
• All settings panels (Editor, Terminal, Files, Network, Git, Debug): Properly handle folderPath prop for folder-scoped read/write/reset operations
• Folder info banner: Shows which folder is being edited with clear visual indicator
• Accessibility: Added aria-label to the folder selector dropdown

Testing

• npm run build ✓
• npx tsc --noEmit ✓
• Verified folder scope reads from getEffectiveSettingsForPath()
• Verified folder scope writes via setFolderSetting()
• Verified folder scope resets via resetFolderSetting()
• Verified override indicators show correctly for folder scope