chore(deps): update dependency @cucumber/fake-cucumber to v18

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@cucumber/fake-cucumber	^16.0.0 -> ^18.0.0

---

Release Notes

cucumber/fake-cucumber (@​cucumber/fake-cucumber)

v18.0.0

Compare Source

Added

• Populate TestRunStarted.id, TestCase.testRunStartedId and TestRunFinished.testRunStartedId on messages
• Populate Hook.type on messages

Changed

• Changed signatures of makeTestCase and makeTestPlan

v17.0.0

Compare Source

Removed

• BREAKING CHANGE: Remove synthetic step for empty pickles (#​125)

v16.5.0

Compare Source

Added

• Add support for link attachments (#​121)

v16.4.0

Compare Source

Added

• Include message prop in result for pending steps (#​106)

v16.3.0

Compare Source

Added

• Support including fileName in attachment (#​92)

v16.2.0

Compare Source

Added

• Upgrade to @cucumber/messages 21
• Add sourceReference to parameterType (#​90)

v16.1.0

Compare Source

Added

• Exception to step result (#​78)
• Upgrade to @cucumber/messages 21
• Upgrade to @cucumber/gherkin 26

---

Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: javascript/package-lock.json

npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @cucumber/[email protected]
npm error Found: @cucumber/[email protected]
npm error node_modules/@cucumber/gherkin
npm error   dev @cucumber/gherkin@"^29.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @cucumber/gherkin@">=30.0" from @cucumber/[email protected]
npm error node_modules/@cucumber/fake-cucumber
npm error   dev @cucumber/fake-cucumber@"^18.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-11-09T05_09_43_322Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-11-09T05_09_43_322Z-debug-0.log