Can't create package version with coverage & dependency: invalid attribute 'subscriberPackageId' at line 1, column 535

### Summary
Running a multi-package setup with a pipeline utilizing flxbl.io, I have however tested this locally too and have run into the same result. Creating a package with coverage and dependency to a managed package (vlocity_cmt) results in the following cryptic error message:

```
Error (1): Multiple errors occurred:
(1) Unable to parse package2-descriptor.json: invalid attribute 'subscriberPackageId' at line 1, column 535
```

Ensured that sf is up to date, and that sfdx-project.json uses API version 61. No change in results.

### Steps To Reproduce

Unable to provide a repo due to the metadata being reserved for a client.
I can however show the structure this follows.

```
src-sales
= core
== data-model
=== main
== util
=== main
= module1
= module2
= module3
src-sales-b2b
= main
src-service
= main
src-ui
= main
```

(This repo is in the process of decomposition)
The package that is currently failing is located in src-sales/core and has a dependency to vlocity_cmt (latest version)
The package contains the following metadata:
* classes
* customMetadata
* LeadConvertSettings
* matchingRules
* objects
* customPermissions
* globalValueSets
* globalValueSetTranslations
* labels
* lwc
* objectTranslations
* workflows

I ran the following command on my machine to get this result:
```
sf package version create -p PACKAGENAME -x -c -v HUBNAME -f config/project-scratch-def.json -w 60
```

### Expected result
The package should be created and receive a coverage report.

### Actual result
Fails with error message mentioned above.

### System Information
Using zsh on MacOS, the VM that also runs into this issue uses ubuntu and the flxbl.io GitHub container.]

```json
{
"architecture": "darwin-arm64",
"cliVersion": "@salesforce/cli/2.44.8",
"nodeVersion": "node-v22.2.0",
"osVersion": "Darwin 23.4.0",
"rootPath": "/opt/homebrew/lib/node_modules/@salesforce/cli",
"shell": "zsh",
"pluginVersions": [
"@oclif/plugin-autocomplete 3.0.18 (core)",
"@oclif/plugin-commands 3.3.4 (core)",
"@oclif/plugin-help 6.0.22 (core)",
"@oclif/plugin-not-found 3.1.10 (core)",
"@oclif/plugin-plugins 5.1.3 (core)",
"@oclif/plugin-search 1.0.24 (core)",
"@oclif/plugin-update 4.2.14 (core)",
"@oclif/plugin-version 2.1.2 (core)",
"@oclif/plugin-warn-if-update-available 3.0.19 (core)",
"@oclif/plugin-which 3.1.10 (core)",
"@salesforce/cli 2.44.8 (core)",
"apex 3.1.13 (core)",
"auth 3.6.17 (core)",
"data 3.4.3 (core)",
"deploy-retrieve 3.8.3 (core)",
"info 3.3.3 (core)",
"limits 3.3.9 (core)",
"marketplace 1.2.8 (core)",
"org 4.1.14 (core)",
"packaging 2.4.5 (user)",
"schema 3.3.9 (core)",
"settings 2.2.7 (core)",
"signups 2.0.13 (link) /opt/homebrew/lib/node_modules/@salesforce/plugin-signups",
"sobject 1.4.6 (core)",
"source 3.3.18 (core)",
"telemetry 3.3.11 (core)",
"templates 56.2.9 (core)",
"trust 3.7.3 (core)",
"user 3.5.11 (core)",
"sfdmu 4.32.2 (user)",
"sfdx-git-delta 5.40.0 (user)"
]
}
```

### Additional information
The first time this came up was when the new release was rolled out to us. We had a version mismatch in our packages, leading me to use `releaseVersion: previous` in our scratch org definition. After this the installation on our lower instance (integration instance) started working again, the build of releasable packages however failed.

What did work was the creation of beta packages. This error seems to be exclusive to release candidate packages.