--allow-tool='shell(docker ps)' doesn't work

### Describe the bug

https://docs.github.com/en/copilot/reference/copilot-cli-reference/cli-command-reference#tool-permission-patterns - documentation mentions `shell(git push)` as an example pattern for --allow-tool. This seems to imply that there's a flexible mechanism for allowing subcommands (we don't have to allow all `git` commands, we can pick specific subcommands like `git push` to allow).

This does work for `git` (I tested it with `git status`) but doesn't work for other commands. For example:
```copilot --model gpt-5-mini --allow-tool='shell(docker ps)' -p 'Run this command in Bash: `docker ps`'```

This doesn't work. Same with `shell(docker ps:*)`

### Affected version

GitHub Copilot CLI 1.0.21.

### Steps to reproduce the behavior

```copilot --model gpt-5-mini --allow-tool='shell(docker ps)' -p 'Run this command in Bash: `docker ps`'```

### Expected behavior

Expected the `docker ps` command to be allowed to run, without asking for permissions. But instead seeing "Permission denied and could not request permission from user"

### Additional context

_No response_

Start by reproducing the reported command with GitHub Copilot CLI 1.0.21, comparing shell(git status) with shell(docker ps) and shell(docker ps:*). Read the tool-permission-patterns documentation linked in the issue and trace the permission-pattern handling entry point. Done means the documented docker ps pattern runs without a permission prompt while unrelated commands remain protected.

Vom Indexierungsmodell aus dem Issue-Text verfasst.