feat(chat): Add header for shell command

[yueny2020]

Problem

• Add header for shell command

Solution

• Screen shots of the new shell command card for un-destructive command

• Screen shots of high risk command

---

• 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.

[laileni-aws]

Do we need confirm-tool-use ?
Can this be replaced with run-shell-command?

[yueny2020]

can remove it in next pr.

[laileni-aws]

I think we can follow similar approach as this for storing body and icon values from messenger.ts.

[yueny2020]

not sure what you want me to follow?

[laileni-aws]

If possible, Can we pass values of body and icon etc in this approach?

[laileni-aws]

Do we need this check ?

message.startsWith('```shell')

[yueny2020]

yes, this is needed, as the execution log also has the ToolType.ExecuteBash.

[Hweinstock]

from failing CI:

Invalid pull request title: `Add header for shell command`

* Problem: missing colon (:) char
* Expected format: `type(scope): subject...`
    * type: one of (build, ci, config, deps, docs, feat, fix, perf, refactor, revert, style, telemetry, test, types)
    * scope: lowercase, <30 chars
    * subject: must be <[10](https://github.com/aws/aws-toolkit-vscode/actions/runs/14256461851/job/39960002171?pr=6939#step:5:11)0 chars
    * documentation: https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#pull-request-title
* Hint: *close and re-open the PR* to re-trigger CI (after fixing the PR title).

[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.