Add option to save conversations to a local project folder

[napter]

Description

When working in many projects, finding past conversations that relate to the current project can be cumbersome.

This adds a workspace option, where users can specify a folder to automatically save their current conversations.

In addition to making it easier to find conversations, a local history of conversations means you can ask Roo to review previous conversations for context in a new task.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• [ x ] New feature
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Checklist:

• [x ] My code follows the patterns of this project
• [ x] I have performed a self-review of my own code
• [ x] I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation

Additional context

Related Issues

Reviewers

---

Important

Adds a feature to save conversations to a specified local folder, with UI and backend support, and includes tests for the new functionality.

• Behavior:
  • Adds conversationSaveFolder setting to save conversations locally in Cline.ts and ClineProvider.ts.
  • Implements ConversationSaver class in conversation-saver/index.ts to handle saving and updating conversations.
  • Updates SettingsView.tsx to include UI for setting conversation save folder.
• Testing:
  • Adds tests for ConversationSaver in conversation-saver/__tests__/index.test.ts.
  • Updates extension.test.ts to ensure new feature integration.
• Misc:
  • Updates package.json to reflect changes.
  • Adjusts ExtensionStateContext.tsx to manage new state for conversation saving.

^{This description was created by for c70faf0. It will automatically update as commits are pushed.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: 7bb587a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[mrubens]

Do you think we should be checking in these documentation files? My instinct is no, but curious to hear your thoughts.