Reorganize example names

Based on public reception, people were immediately opening up the
"simplest name" looking one, and then taken aback by the low-level JNI
bridging full of unsafe code and cdecl etc. We should make it clear that
those examples are just that: low level and raw jni examples, as
compared to other ones using swift-java interop.

It should be easier to discover the swift-java example, because that
provides a better first impression, and long term user experience.

Author: ktoso

README.md

@@ -40,7 +40,6 @@ android {
 }
 
 dependencies {
-
     implementation(libs.androidx.core.ktx)
     implementation(libs.androidx.lifecycle.runtime.ktx)
     implementation(libs.androidx.activity.compose)
@@ -49,7 +48,7 @@ dependencies {
     implementation(libs.androidx.ui.graphics)
     implementation(libs.androidx.ui.tooling.preview)
     implementation(libs.androidx.material3)
-    implementation(project(":hashing-lib"))
+    implementation(project(":hello-swift-java-hashing-lib"))
     testImplementation(libs.junit)
     androidTestImplementation(libs.androidx.junit)
     androidTestImplementation(libs.androidx.espresso.core)