feat: expose askQuestion on plugin tool context

[jquense]

What does this PR do?

Exposes Question.ask on the plugin tool context, so custom tools can ask questions. closes #13786 alternative to #12046

If you paste a large clearly AI generated description here your PR may be IGNORED or CLOSED!

How did you verify your code works?

Added a test tool and ran bun dev

[github-actions]

Hey! Your PR title Expose askQuestion on plugin tool context doesn't follow conventional commit format.

Please update it to start with one of:

• feat: or feat(scope): new feature
• fix: or fix(scope): bug fix
• docs: or docs(scope): documentation changes
• chore: or chore(scope): maintenance tasks
• refactor: or refactor(scope): code refactoring
• test: or test(scope): adding or updating tests

Where scope is the package name (e.g., app, desktop, opencode).

See CONTRIBUTING.md for details.

[github-actions]

The following comment was made by an LLM, it may be inaccurate:

Potential Related PRs Found

The following PRs appear to be related to this feature:

1. feat(plugin): add optional askPermission to ToolContext (feat(plugin): add optional askPermission to ToolContext #6042)

   • Related because it also adds context methods to plugin tools

2. feat(core): expose Question.ask via API/SDK (feat(core): expose Question.ask via API/SDK  #12046)

   • Related because it also exposes the Question.ask functionality, though at a different level (API/SDK vs plugin context)

3. feat(plugin): align plugin tool types with built-in tool capabilities (feat(plugin): align plugin tool types with built-in tool capabilities #12050)

   • Related because it addresses aligning plugin tool capabilities with built-in tools, which may include question-asking functionality

These PRs address similar patterns of exposing capabilities to plugin tools, though none appear to be exact duplicates of PR #13755. Consider reviewing these to ensure no overlapping work or conflicting implementations.

[github-actions]

Thanks for your contribution!

This PR doesn't have a linked issue. All PRs must reference an existing issue.

Please:

1. Open an issue describing the bug/feature (if one doesn't exist)
2. Add Fixes #<number> or Closes #<number> to this PR description

See CONTRIBUTING.md for details.