chore(ui): reenable jvm

Makes the build less confusing; android builds will still succeed, but
jvm ones will fail (for now)

ui/build.gradle.kts

@@ -18,7 +18,7 @@ kotlin {
         }
     }
     
-//    jvm()
+    jvm()
     
     sourceSets {
         androidMain.dependencies {
@@ -32,7 +32,13 @@ kotlin {
             implementation(project(":core"))
             implementation(libs.compose.runtime)
             implementation(libs.compose.foundation)
+
+            // TODO: Desktop will not build
+            // Using upstream jetpack material3 for expressive list items in 1.5.0-alpha11
+            // At time of writing, cmp material3 is still on 1.5.0-alpha10
             implementation(libs.compose.material3.google)
+            // implementation(libs.compose.material3)
+
             implementation(libs.compose.ui)
             implementation(libs.compose.components.resources)
             implementation(libs.compose.uiToolingPreview)
@@ -51,10 +57,10 @@ kotlin {
         commonTest.dependencies {
             implementation(libs.kotlin.test)
         }
-//        jvmMain.dependencies {
-//            implementation(compose.desktop.currentOs)
-//            implementation(libs.kotlinx.coroutinesSwing)
-//        }
+        jvmMain.dependencies {
+            implementation(compose.desktop.currentOs)
+            implementation(libs.kotlinx.coroutinesSwing)
+        }
     }
 }