Fix refresh after manualy changing task context

[JonasHelming]

What it does

Fix a refresh bug for task context. If you work with an AI created task context and change it manually, the agent still works with the old version after saving the file (see how to test)

How to test

Before:

• Create a task context with architect
• Change it manually (e.g. add a new step)
• Run Coder (F1 => Chat: Task Context: Initiate Session)
• Observe that the change is not reflected. You can also stop the agent and ask to print out the task context
  After:
  The above case works reflecting the change

Follow-ups

I removed the cache for task context content, which I thin is a pragmatic solution. However, this might point to an issue with the file watcher we should investigate potentially..

Breaking changes

• This PR introduces breaking changes and requires careful review. If yes, the breaking changes section in the changelog has been updated.

Attribution

Review checklist

• As an author, I have thoroughly tested my changes and carefully followed the review guidelines
• User-facing text is internationalized using the nls service (for details, please see the Internationalization/Localization section in the Coding Guidelines)

Reminder for reviewers

• As a reviewer, I agree to behave in accordance with the review guidelines

[ndoschek]

Thanks, LGTM!
I tested the example scenario a few times and it worked fine for me, the updated task context is used immediately now.

I just have a minor comment inline, would be great if you could have a quick look.

[ndoschek]

Thanks for the quick update! LGTM 👍