feat: add repository_dispatch to update CLI version on GitHub Action repos

[jonathannorris]

Summary

• Adds repository_dispatch events to the CLI release workflow that trigger CLI version updates on feature-flag-pr-insights-action and feature-flag-code-usage-action
• Gated on minor or patch releases, matching the existing vscode-extension update behavior
• Fixes server.json formatting and uses jq --indent 4 in the release workflow to prevent future drift

The target repos will each have a receiver workflow that handles the update, rebuilds dist/, and opens a PR.

[Copilot]

Pull request overview

This PR extends the existing CLI release workflow to notify downstream GitHub Action repositories to update their pinned CLI version whenever a minor or patch release is cut, aligning with the current VSCode extension update behavior.

Changes:

• Add two repository_dispatch steps to trigger update-cli-version in feature-flag-pr-insights-action.
• Add two repository_dispatch steps to trigger update-cli-version in feature-flag-code-usage-action.
• Gate both dispatches to run only for minor and patch workflow_dispatch releases.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 comment.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

npm-version input name contains a hyphen, so references like inputs.npm-version are parsed as an expression with - (subtraction) rather than property access. This will cause the if: condition (and any other use of this input) to evaluate incorrectly or fail. Use bracket notation (inputs['npm-version']) for the condition (and update other references in this workflow for consistency).