`--include-locked` and `-l` works differently

[Perdolique]

Describe the bug

According to --help, option --include-locked and its short version -l should be handled the same way, but it doesn't.

• taze version 19.1.0

❯ npx taze -l latest

node-starter - 1 major

  devDependencies
    @types/node    ~5d  22.15.30  →  24.0.0  ⩽1d

npx taze --include-locked latest

node-starter - 1 patch

  devDependencies
    @types/node    ~5d  22.15.30  →  22.15.31  ⩽1d  (24.0.0 available)

Reproduction

https://stackblitz.com/edit/taze-include-locked-bug

System Info

System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 20.19.1 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.8.2 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm

Used Package Manager

npm

Validations

• Follow our Code of Conduct
• Read the Contributing Guide.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
• The provided reproduction is a minimal reproducible of the bug.

Contributions

• I am willing to submit a PR to fix this issue
• I am willing to submit a PR with failing tests (actually just go ahead and do it, thanks!)