feat(chat): Grouping read and list directory messages UX

[laileni-aws]

Problem:

We identified and fixed an issue where the IDE's UI would prematurely stop displaying when executing certain commands. This occurred specifically when the Language Model (LLM) attempted to run the executeBash command before the Read/List Directory tools.

Example:

When a user asks "write a script that tells me whoami", the operation only requires the fsWrite command and not any directory reading tools. In such cases, the IDE would execute fsWrite but fail to display the executeBash tool in the chat interface. This UI behavior has been corrected in this PR, along with improvements to the Reading File user experience.

• Major changes lies in this commit in ChatStream.ts

        // For FsRead and ListDirectory tools If messageIdToUpdate is undefined, we need to first create an empty message with messageId so it can be updated later
        if (isReadorList && !messageIdToUpdate) {
            this.messenger.sendInitialToolMessage(tabID, triggerID, toolUse?.toolUseId)
        } else {
            this.messenger.sendInitalStream(tabID, triggerID)
        }

---

• Treat all work as PUBLIC. Private feature/x branches will not be squash-merged at release time.
• Your code changes must meet the guidelines in CONTRIBUTING.md.
• License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

[github-actions]

• This pull request modifies code in src/* but no tests were added/updated.
  • Confirm whether tests should be added or ensure the PR description explains why tests are not required.
• This pull request implements a feat or fix, so it must include a changelog entry (unless the fix is for an unreleased feature). Review the changelog guidelines.
  • Note: beta or "experiment" features that have active users should announce fixes in the changelog.
  • If this is not a feature or fix, use an appropriate type from the title guidelines. For example, telemetry-only changes should use the telemetry type.

[Hweinstock]

What is the regression that this fixes? Didn't see it mentioned in the revert PR so missing some context here. How does creating an empty message fix this?

[laileni-aws]

What is the regression that this fixes? Didn't see it mentioned in the revert PR so missing some context here. How does creating an empty message fix this?

Problem:

We identified and fixed an issue where the IDE's UI would prematurely stop displaying when executing certain commands. This occurred specifically when the Language Model (LLM) attempted to run the executeBash command before the Read/List Directory tools.

Example:

When a user asks "write a script that tells me whoami", the operation only requires the fsWrite command and not any directory reading tools. In such cases, the IDE would execute fsWrite but fail to display the executeBash tool in the chat interface. This UI behavior has been corrected in this PR, along with improvements to the Reading File user experience.

[laileni-aws]

/retryBuilds

[Hweinstock]

Thanks for adding the explanation, thats super helpful!

It seems to me that the heavy conditional logic based on which tool is being used feels like the real problem here as it makes the expected behavior unclear and hard to follow.

However, this is a broader issue we can address in migration to Flare.