Remove v1 release steps from documentation release process

[Copilot]

Jaeger v1 releases are discontinued. Remove v1-specific steps from the release workflow and scripts.

Changes

• .github/workflows/ci-release.yml: Remove version_v1 input parameter; update script invocation and PR naming to v2-only
• scripts/release.sh:
  • Accept single v2 version argument instead of two
  • Remove gen_cli_docs_v1() function and Docker-based CLI doc generation
  • Remove v1/v2 processing loop, directly handle v2 only
  • Remove ./data/cli/ from git staging
• RELEASE.md: Update instructions to reference v2 only; remove CLI flags auto-generation section

Usage

# Before (required both versions)
./scripts/release.sh 1.77.0 2.14.0

# After (v2 only)
./scripts/release.sh 2.14.0

Original prompt

When performing future release we will no longer be creating new v1 versions, including running v1 binaries to generate updates to their CLIs. so remove these steps from the release process, including requirement for v1 input variable

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.