Native artifacts are pulling transitive dependencies

Minor issue, but ideally the native artifacts (JAR) should be pulling in any dependencies into the project, only the non-native JAR (i.e. with a classifier) should do.

Hi @karllessard, I've recently been working with @mihaimaruseac on the legacy JNI packaging cleanup in the main TensorFlow repo (#108284). I'd like to help resolve this dependency issue in the new Java repo.

To ensure the native artifacts are correctly decoupled, should I look into adding true to these dependencies in the native module POMs, or would you prefer moving them to a provided scope for the platform-specific classifiers? I'm happy to submit a PR once I verify the dependency tree locally.