fix(cli): include release scripts in CLI release paths

What changed

The dedicated CLI Release workflow now triggers when CLI release infrastructure changes, not only when CLI source/package files change. The trigger now includes:

• mise/tasks/cli/**
• mise/tasks/release/components.json
• .github/workflows/cli-release.yml
• .github/workflows/cli-build-publish.yml

The CLI component in mise/tasks/release/components.json uses the same additional paths, so mise run release:check cli marks these changes as releasable.

The CLI release notes and changelog generation in cli-build-publish.yml now use the expanded include-path set too. The broad Release workflow ignores CLI-only release script/workflow changes so future CLI packaging-only changes do not wake the non-CLI release pipeline unnecessarily.

Why

tuist/tuist#11235 changed only mise/tasks/cli/bundle.sh. The broad Release workflow ran and release:check correctly identified cli as releasable, but that workflow does not publish CLI artifacts. The dedicated CLI Release workflow did not run because its paths filter excluded mise/tasks/cli/**.

That meant the packaging fix merged without a post-fix CLI release being built.

Impact

Future CLI packaging or CLI release workflow changes will trigger the dedicated CLI release pipeline and produce a release. Merging this PR should also trigger a CLI release because it changes paths now owned by the CLI component.

Validation

• git diff --check
• ruby -e 'require "yaml"; ARGV.each { |path| YAML.load_file(path); puts "ok #{path}" }' .github/workflows/cli-release.yml .github/workflows/cli-build-publish.yml .github/workflows/release.yml
• mise run release:check cli
  • confirmed latest tag 4.199.0
  • confirmed next version 4.199.1
  • confirmed release? true