Add submitUserMessage to Task

[mrubens]

Important

Adds submitUserMessage method to Task class for submitting user messages to a webview, with tests for various scenarios.

• Behavior:
  • Adds submitUserMessage method to Task class in Task.ts to submit user messages to a webview.
  • Handles empty messages by not sending them.
  • Logs an error if the provider reference is lost.
• Interfaces:
  • Adds submitUserMessage to TaskLike interface in task.ts.
• Tests:
  • Adds tests in Task.spec.ts to verify submitUserMessage behavior, including handling of empty messages and undefined providers.
• Versioning:
  • Updates version in package.json from 1.44.0 to 1.45.0.

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

[roomote]

Thank you for your contribution! I've reviewed the changes and found this to be a well-implemented feature. The code is clean, properly tested, and follows established patterns. I have a few minor suggestions for improvement.

[roomote]

Consider simplifying the null handling here. You're using text ?? "" but then checking !trimmed. This could be simplified:

Suggested change

	const trimmed = (text ?? "").trim()
	const trimmed = text?.trim() || ""
	const imgs = images || []
	if (!trimmed && imgs.length === 0) {
	return
	}

This would be more consistent with how you handle the images parameter.

[roomote]

Consider adding JSDoc documentation for this public method to maintain consistency with other public methods and improve IDE tooltips:

Suggested change

	public submitUserMessage(text: string, images?: string[]): void {
	/**
	* Submits a user message to the webview.
	* @param text - The message text to submit
	* @param images - Optional array of image paths to include with the message
	*/
	public submitUserMessage(text: string, images?: string[]): void {

[roomote]

Good test coverage! Consider adding one more test case for completeness - testing the scenario where only images are provided without text:

it("should handle images-only messages", async () => {
  const task = new Task({
    provider: mockProvider,
    apiConfiguration: mockApiConfig,
    task: "initial task",
    startTask: false,
  })

  // Call with images but no text
  task.submitUserMessage("", ["image1.png", "image2.png"])

  // Should not call postMessageToWebview since text is empty
  expect(mockProvider.postMessageToWebview).not.toHaveBeenCalled()
})

This would ensure the edge case is explicitly tested, even though the current implementation handles it correctly.