feat: Add automatic configuration import on extension startup

[takakoutso]

Related GitHub Issue

Closes: #4792

Description

Test Procedure

Type of Change

• 🐛 Bug Fix: Non-breaking change that fixes an issue.
• ✨ New Feature: Non-breaking change that adds functionality.
• 💥 Breaking Change: Fix or feature that would cause existing functionality to not work as expected.
• ♻️ Refactor: Code change that neither fixes a bug nor adds a feature.
• 💅 Style: Changes that do not affect the meaning of the code (white-space, formatting, etc.).
• 📚 Documentation: Updates to documentation files.
• ⚙️ Build/CI: Changes to the build process or CI configuration.
• 🧹 Chore: Other changes that don't modify src or test files.

Pre-Submission Checklist

• Issue Linked: This PR is linked to an approved GitHub Issue (see "Related GitHub Issue" above).
• Scope: My changes are focused on the linked issue (one major feature/fix per PR).
• Self-Review: I have performed a thorough self-review of my code.
• Code Quality:
  • My code adheres to the project's style guidelines.
  • There are no new linting errors or warnings (npm run lint).
  • All debug code (e.g., console.log) has been removed.
• Testing:
  • New and/or updated tests have been added to cover my changes.
  • All tests pass locally (npm test).
  • The application builds successfully with my changes.
• Branch Hygiene: My branch is up-to-date (rebased) with the main branch.
• Documentation Impact: I have considered if my changes require documentation updates (see "Documentation Updates" section below).
• Changeset: A changeset has been created using npm run changeset if this PR includes user-facing changes or dependency updates.
• Contribution Guidelines: I have read and agree to the Contributor Guidelines.

Screenshots / Videos

Documentation Updates

Additional Notes

Get in Touch

---

Important

Refactor autoImportConfig to consolidate provider settings, update tests, and improve error handling.

• Refactoring:
  • Consolidate providerSettingsManager and contextProxy into provider in autoImportConfig() in autoImportConfig.ts.
  • Update importConfigFromPath() to use provider for settings management.
• Testing:
  • Update mocks in autoImportConfig.spec.ts to reflect changes in autoImportConfig.ts.
  • Add tests for handling invalid JSON and file system errors.
• Misc:
  • Remove unused eslint-disable comment in global.d.ts.
  • Adjust activate() in extension.ts to pass provider to autoImportConfig().

^{This description was created by for 19be0d2. You can customize this summary. It will automatically update as commits are pushed.}

[takakoutso]

Hi! I've gone ahead and implemented the items from the issue I posted. I think there is also an opportunity to introduce schema versioning and potentially schema migration scripts into RooCode. In my use case, I've encountered issues where the RooCode config updates frequently, breaking older configs. A way to introduce schema versioning and ways to keep track of the range of schema versions that are supported for a given RooCode release would help greatly. Please let me know if there's a need for this, and I would be more than glad to tackle that in this issue/MR or another one. Thanks!

[daniel-lxs]

Hey @takakoutso, thank you for the PR!
I took a look at it and left a couple of suggestions.

Let me know what you think!

[takakoutso]

Hi @daniel-lxs, thank you for your review! I went ahead and made some adjustments. I would love to hear what you think. Thanks!

[daniel-lxs]

Hey @takakoutso, It looks like your latest commit introduced unrelated changes.

Can you take a look or do you want me to fix them for you?

[daniel-lxs]

Thank you @takakoutso for fixing the failing test!

Looks good to me!

[mrubens]

Looks like some conflicts snuck in here