refactor(storage): deprecate LogicalDType, fromDType/toLogicalDType, logicalType getters and overloads (SKEEP-003 P0, S0.2b)

[michalharakal]

Summary

SKEEP-003 slice S0.2b (milestone M0 #1001, decision #13), the last Phase-0 step: with the two-way bridge (#1045), the DType witness (#1050), Format (#1051) and AllocationSpec (#1053) in place, nothing new is written against LogicalDType — so it is now deprecated, additively.

• @Deprecated(WARNING, ReplaceWith("DType")) on LogicalDType, LogicalDType.fromDType, DType.toLogicalDType(), the logicalType properties of TensorStorage / StorageMemoryReport, the LogicalDType overloads of TensorStorageFactory (fromRawBytes, fromRawBytesOwned, fileBacked) and PackedBlockStorage.toTensorStorage(logicalType, …).
• Nothing removed: the primary constructors keep LogicalDType (a data-class constructor cannot change compatibly) and every shim delegates to the dtype-first API; removal is scheduled for the next major (deprecate-don't-delete).
• The files that implement the legacy surface (LogicalDType.kt, LogicalDTypeBridge.kt, TensorStorage.kt, StorageMemoryReport.kt, TensorStorageFactory.kt, PackedBlockStorage.kt, StorageSpec.kt) and the 16 tests that keep it covered carry a file-level @Suppress("DEPRECATION") with the reason; the rest of the build is deprecation-warning-free for LogicalDType (checked on the JVM compile log).
• No BCV change (annotations are not part of the dumps); no CHANGELOG edit.

Stacked on #1057 (S0.8); retarget to develop after it merges.

Test plan

Full local gate (scripts/pr-gate.sh, JDK 25); results in the first comment. Targeted: lang-core storage/types + io-gguf + io-safetensors jvmTest 503/503.

Closes #1014

🤖 Generated with Claude Code

[michalharakal]

Local gate scripts/pr-gate.sh (JDK 25) on the pre-rebase tree ae658b16 (identical sources; the rebase onto the updated chain only changed upstream API dumps):

=== pr-gate: JVM tests ===                                      BUILD SUCCESSFUL in 6m 29s
=== pr-gate: apiCheck ===                                       BUILD SUCCESSFUL in 1m 49s
=== pr-gate: verifyNpmPins jsTest wasmJsTest wasmWasiTest ===   BUILD SUCCESSFUL in 2m 36s
=== pr-gate: linuxX64Test ===                                   BUILD SUCCESSFUL in 1m 30s
=== pr-gate: assemble ===                                       BUILD SUCCESSFUL in 2m 10s
=== pr-gate: :skainet-test:skainet-test-java:test ===           BUILD SUCCESSFUL in 21s
pr-gate: all legs passed.

A --quick re-run (jvmTest + apiCheck) on the rebased tip follows in the next comment.

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

[michalharakal]

Confirmation on the rebased tip eda8cad: scripts/pr-gate.sh --quick — jvmTest ✔ · apiCheck ✔ (all tasks up-to-date/from cache against the full run above; the rebase changed no source).