Add `/tools` command to list all available tools

### Checks

- [x] I have searched [github.com/aws/amazon-q-developer-cli/issues](https://github.com/aws/amazon-q-developer-cli/issues?q=) and there are no duplicates of my issue
- [x] I have run `q doctor` in the affected terminal session
- [x] I have run `q restart` and replicated the issue again

### Operating system

Linux 5.10.234-206.921.amzn2int.x86_64 - Amazon Linux 2

### Expected behaviour

When typing `/tools` in the chat, Amazon Q should display a list of all available tools and commands that can be used in the current context, similar to how `ls` shows files in a directory.

### Actual behaviour

Currently there is no built-in way to see a comprehensive list of all available tools and commands within the Amazon Q CLI interface.

```
[chat-transcript]
> /tools list

> show all tools

I'll show you all the tools available to me. Let me list them for you:

1. **execute_bash** - Executes bash commands in your environment
2. **fs_read** - Reads files and directories (similar to cat, ls)
3. **report_issue** - Opens a browser to report issues with the chat
4. **use_aws** - Makes AWS CLI API calls
5. **fs_write** - Creates and edits files

Each tool has specific parameters and capabilities:

- **execute_bash**: Runs any bash command you specify
- **fs_read**: Can show file contents, list directories, or search in files
- **report_issue**: Creates GitHub issues with pre-filled information
- **use_aws**: Interacts with AWS services via the CLI
- **fs_write**: Creates new files, appends to files, or replaces content in files

Is there a specific tool you'd like to use or learn more about?
[Tool uses: none]

> issue

It seems you're interested in the report_issue tool. This tool allows you to report issues, bugs, or feature requests related to Amazon Q by opening a pre-filled GitHub issue template.

To use this tool, you need to provide a title for the issue, and you can optionally include:
- The actual behavior you observed (what happened)
- The expected behavior (what should have happened)
- Steps to reproduce the issue

Would you like me to help you create an issue report? If so, please provide:
1. A title for the issue
2. Any details about what happened vs. what you expected
3. Steps that led to the issue
[Tool uses: none]

> /help

> /context show

> /clear

> /issue

I'd be happy to help you report an issue or make a feature request for Amazon Q. You can use the built-in reporting feature to submit your feedback directly to the GitHub repository.

To proceed, I'll need a bit more information about what you'd like to report:

1. Would you like to report a bug/issue or request a new feature?
2. Could you provide some details about the issue you're experiencing or the feature you'd like to see?
3. If it's an issue, what behavior are you seeing, and what did you expect to happen instead?

Once you provide these details, I can help you submit a properly formatted report using the `report_issue` function, which will create a pre-filled GitHub issue with your feedback and relevant context from this conversation.
[Tool uses: none]

> /tools should have list & ls to show all tools list

> issue

I'd be happy to help you report an issue with Amazon Q. To create a detailed and helpful issue report, I'll need a bit more information:

1. What specific issue are you experiencing with Amazon Q?
2. What were you trying to do when the issue occurred?
3. What behavior did you expect, and what happened instead?

The more details you can provide, the better the development team will be able to understand and address your issue. Once you share these details, I'll help you submit a properly formatted issue report.
[Tool uses: none]

> `/tools` feature should list & ls to show all tools

Thank you for sharing your feature request. I understand you'd like to have a `/tools` command that would list all available tools, similar to how `ls` shows files in a directory.

Let me help you submit this as a feature request:
[Tool uses: report_issue]
```

### Steps to reproduce

_No response_

### Environment

```yaml

[q-details]
version = "1.7.3"
hash = "3e4ae79d371315e80ddac772b43fff2cba314104"
date = "2025-04-10T05:47:26.052106Z (1d ago)"
variant = "minimal"

[system-info]
chip = "AMD EPYC 9R14"
total-cores = 4
memory = "15.25 GB"

[system-info.os.linux]
kernel_version = "5.10.234-206.921.amzn2int.x86_64"
id = "amzn"
name = "Amazon Linux"
pretty_name = "Amazon Linux 2"
version_id = "2"
version = "2"
variant = "internal"

[environment]
cwd = "/local/home/USER"
cli-path = "/local/home/USER"
os = "Linux"
shell-path = "/local/home/USER/.toolbox/tools/toolbox/1.1.1762.0/toolbox-exec"
shell-version = "5.8"
install-method = "toolbox"
in-ssh = true

[env-vars]
PATH = "/home/USER/.local/share/mise/installs/node/18.20.2/bin:/home/USER/.local/share/mise/installs/python/3.12/bin:/home/USER/.local/share/mise/installs/python/3.11/bin:/home/USER/.local/share/mise/installs/python/3.10/bin:/home/USER/.local/share/mise/installs/python/3.9/bin:/home/USER/.local/share/mise/installs/python/3.8/bin:/home/USER/.toolbox/bin:/home/USER/.cargo/bin:/usr/local/bin:/usr/bin:/home/USER/bin:/usr/local/sbin:/usr/sbin:/home/USER/.local/bin:/home/USER/bin"
QTERM_SESSION_ID = "2a1504e6423c48bea4050511c63a43b3"
Q_PARENT = "/tmp/q-parent-39cd95bafbb344899c7e6b663d8ed8eb.socket"
Q_SET_PARENT_CHECK = "1"
Q_TERM = "1.7.2"
SHELL = "/bin/zsh"
TERM = "xterm-256color"

[chat-settings]
interactive=true

[chat-trusted_tools]

[chat-failed_request_ids]
none

[chat-context]
current_profile=default
profiles=
default

global_context=
.amazonq/rules/**/*.md
README.md
AmazonQ.md

profile_context=none

files=none
```