[BUG] Maven bip32-ed25519 1.8.8 source mapping and Windows x86-64 native

### Description

Maven Central currently serves `org.hyperledger.identus:bip32-ed25519:1.8.8`, but I could not map that artifact to a published Git tag, `scm.revision`, or GitHub release. Tags exist for `v1.8.0`, `v1.8.5`, and `v1.8.7`; there is no `v1.8.8` tag or release.

Two related observations from the published 1.8.8 artifacts:

1. The `-sources` jar contains generated UniFFI Kotlin bindings, not the Rust wrapper sources, `Cargo.lock`, or other native build inputs used to produce `uniffi_ed25519_bip32_wrapper`.
2. The JVM jar ships Darwin and Linux natives, but no `win32-x86-64` DLL for `uniffi_ed25519_bip32_wrapper`.

The published UniFFI binding surface appears to be contract version 26 with function checksums 39213 / 33531 / 567. That helps match a rebuild, but it is not a source-to-artifact mapping.

Could the maintainers:

- Identify and attest the exact source commit and workflow inputs that produced Maven `1.8.8`?
- Provide or pin the Rust wrapper lockfile and toolchain inputs used for that build?
- Say whether a Windows x86-64 native is planned for this artifact line?

Until that mapping exists, downstream consumers should not describe a self-built Windows DLL as an Identus 1.8.8 artifact.

Related: draft PR #225 covers Kotlin 1.9 compatibility work around the 1.8.8 line, but does not appear to address source provenance or Windows natives.

### Version

`org.hyperledger.identus:bip32-ed25519:1.8.8`

Start by inspecting the published Maven 1.8.8 artifact and its metadata, then compare it with the repository tags and the inputs associated with draft PR #225. Done means documenting the exact source commit and reproducible Rust/toolchain inputs, and recording the maintainers’ decision about a Windows x86-64 native for this artifact line.

Written by the indexing model from the issue text.