Update dependency @sap-ai-sdk/ai-api to v2

[renovate]

Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.

This PR contains the following updates:

Package	Change	Age	Confidence
@​sap-ai-sdk/ai-api	1.18.0 -> 2.0.0

---

Configuration

📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

This change upgrades the @sap-ai-sdk/ai-api package from version 1.18.0 to 2.0.0 in both the pr-review and pr-summary modules, aligning with the latest SDK release and preparing the tools for new features or improvements introduced in the major version bump.

Walkthrough

• Chore: Bumped the @sap-ai-sdk/ai-api dependency to 2.0.0 in pr-review and pr-summary to leverage updated SDK capabilities and ensure compatibility with recent enhancements.

_{Model: o4-mini | Prompt Tokens: 460 | Completion Tokens: 571}

[github-actions]

Here is friendly feedback on your code enhanced by AI insights. Some suggestions reflect likely patterns, not guaranteed rules, so feel free to apply only what suits your project. Your judgment leads the way. AI is here to support you.
_{Model: o4-mini | Prompt Tokens: 1729 | Completion Tokens: 3314}

[github-actions]

You’ve bumped @sap-ai-sdk/ai-api from 1.18.0 to 2.0.0, which is a major version upgrade and may include breaking changes. Please:

1. Verify compatibility with the orchestration SDK and other code that imports ai-api. If necessary, update any initialization options or method signatures that changed in v2.0.0.
2. Add a semver range (e.g., ^2.0.0) instead of pinning to 2.0.0 to allow patch updates:

"@sap-ai-sdk/ai-api": "^2.0.0",

3. Run your integration tests (or manually smoke-test key workflows) to ensure no regressions.
4. Don’t forget to commit the updated lockfile after installing.

[github-actions]

This file applies the same major dependency bump. To keep consistency and avoid drift:

1. Ensure both workspaces share the same version requirements. Consider extracting shared dependencies into a root package.json if you’re using a monorepo.
2. Use a caret range for patch releases:

"@sap-ai-sdk/ai-api": "^2.0.0",

3. Verify that any code paths consuming the AI API in summary mode have been updated for v2.0.0 changes.
4. Commit the updated lockfile after running npm install to reflect this change.