Modernize release scripts with package updates and compatibility fixes

[tarunramsinghani]

• Update all npm dependencies to latest versions:

  • @octokit/rest: v16.43.2 → v22.0.0
  • @octokit/graphql: v7.1.1 → v9.0.1
  • azure-devops-node-api: v12.0.0 → v15.1.1
  • azure-pipelines-task-lib: v4.3.1 → v5.2.1
  • node-getopt: v0.2.3 → v0.3.2

• Fix createReleaseBranch.js compatibility with new @octokit versions:

  • Remove fetch parameter from GraphQL configuration
  • Implement selective dry-run mode (execute git operations except push)
  • Improve writeAgentVersionFile to always write file

• Optimize createAdoPrs.js dependencies and functionality:

  • Replace got v14 with Node.js native fetch API
  • Remove got and node-fetch dependencies completely
  • Fix Azure DevOps API calls to respect dry-run mode properly

• Enhance util.js error handling:

  • Add graceful handling for missing _hashes directory
  • Provide informative warnings for missing hash files

• Comprehensive testing of all release scripts:

  • Verified fillReleaseNotesTemplate.js functionality
  • Tested rollrelease.js with GitHub PAT authentication
  • Validated createAdoPrs.js with improved dry-run behavior
  • Fixed npm audit security vulnerabilities

All scripts now work correctly with updated dependencies and proper dry-run modes for safe testing.

Context

Explain the context or motivation behind this PR. Include links to any related Azure DevOps Work Items or GitHub issues.
📌 How to link to ADO Work Items

---

Description

Provide a concise summary of the changes introduced in this PR.

---

Risk Assessment (Low / Medium / High)

Assess the risk level and justify your assessment. For example: code path sensitivity, usage scope, or backward compatibility concerns.

---

Unit Tests Added or Updated (Yes / No)

Indicate whether unit tests were added or modified to reflect the changes.

---

Additional Testing Performed

List manual or automated tests performed beyond unit tests (e.g., integration, scenario, regression).

---

Change Behind Feature Flag (Yes / No)

Can this change be behine feature flag, if not why?

---

Tech Design / Approach

• Design has been written and reviewed.
• Any architectural decisions, trade-offs, and alternatives are captured.

---

Documentation Changes Required (Yes/No)

Indicate whether related documentation needs to be updated.

• User guides, API specs, system diagrams, or runbooks are updated.

---

Logging Added/Updated (Yes/No)

• Appropriate log statements are added with meaningful messages.
• Logging does not expose sensitive data.
• Log levels are used correctly (e.g., info, warn, error).

---

Telemetry Added/Updated (Yes/No)

• Custom telemetry (e.g., counters, timers, error tracking) is added as needed.
• Events are tagged with proper metadata for filtering and analysis.
• Telemetry is validated in staging or test environments.

---

Rollback Scenario and Process (Yes/No)

• Rollback plan is documented.

---

Dependency Impact Assessed and Regression Tested (Yes/No)

• All impacted internal modules, APIs, services, and third-party libraries are analyzed.
• Results are reviewed and confirmed to not break existing functionality.

[tarunramsinghani]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).