chore: update dependencies for Capacitor 9

[OS-ruimoreiramendes]

Description

Prepares the next branch for Capacitor 9 work by aligning the dependency declarations:

• Package.swift: bump capacitor-swift-pm to its Capacitor 9 line (9.0.0-alpha.0) and drop the Cordova product.
• package.json: switch @capacitor/{android,core,ios} devDependencies to next and bump @capacitor/core peerDependency to >=9.0.0-alpha.0.

Refs: RMET-5263

Change Type

• Fix
• Feature
• Refactor
• Breaking Change
• Documentation
• Other (CI, chores, etc.)

Rationale / Problems Fixed

The haptics next branch is currently aligned with Capacitor 8 dependencies and is not ready for Cap 9 work.

[OS-pedrogustavobilro]

Just a note regarding the squash-commit message / release, depending on how / when we'll want to release the major for this plugin, we may want to add a BREAKING CHANGE: <explain why it's a breaking change> to the squash-commit footer, and/or do something other than chore: for the connotation.

But then again, the way this repo is set up for release on next, it will try to release as soon as there's new commits, which maybe we don't want, but it's how it is today.

[OS-ruimoreiramendes]

Just a note regarding the squash-commit message / release, depending on how / when we'll want to release the major for this plugin, we may want to add a BREAKING CHANGE: <explain why it's a breaking change> to the squash-commit footer, and/or do something other than chore: for the connotation.

But then again, the way this repo is set up for release on next, it will try to release as soon as there's new commits, which maybe we don't want, but it's how it is today.

Fair point, for this PR I think the better way is to keep it as chore without a BREAKING CHANGE footer so semantic-release skips it.
The plugin isn't fully Cap 9 ready yet (Android baselines, iOS deployment target, podspec, etc., tracked under RMET-4747). When that wider alignment lands, that PR can carry the BREAKING CHANGE and trigger the 9.0.0-alpha.0 release on a fully-aligned plugin.

[OS-pedrogustavobilro]

Makes sense to me @OS-ruimoreiramendes!