chore: remove ComposeTestActivity and LegacyTestActivity from example app

Debug activities that import app.rive.* directly, causing the example
app to need an explicit rive-android dependency. Easy to recreate
when needed for native SDK debugging.

Author: mfazekas

example/android/app/build.gradle

@@ -1,6 +1,5 @@
 apply plugin: "com.android.application"
 apply plugin: "org.jetbrains.kotlin.android"
-apply plugin: "org.jetbrains.kotlin.plugin.compose"
 apply plugin: "com.facebook.react"
 
 /**
@@ -108,10 +107,6 @@ android {
             keyPassword 'android'
         }
     }
-    buildFeatures {
-        compose true
-    }
-
     buildTypes {
         debug {
             signingConfig signingConfigs.debug
@@ -135,11 +130,4 @@ dependencies {
     } else {
         implementation jscFlavor
     }
-
-    // Compose dependencies for ComposeTestActivity
-    implementation(platform("androidx.compose:compose-bom:2023.10.00"))
-    implementation("androidx.activity:activity-compose:1.9.0")
-    implementation("androidx.compose.ui:ui")
-    implementation("androidx.compose.foundation:foundation")
-    implementation("androidx.compose.runtime:runtime")
 }

example/android/app/src/main/AndroidManifest.xml

@@ -22,21 +22,5 @@
             <category android:name="android.intent.category.LAUNCHER" />
         </intent-filter>
       </activity>
-      <activity
-        android:name=".ComposeTestActivity"
-        android:label="Compose Rive Test"
-        android:exported="true"
-        android:theme="@style/AppTheme">
-        <intent-filter>
-            <action android:name="android.intent.action.VIEW" />
-            <category android:name="android.intent.category.DEFAULT" />
-        </intent-filter>
-      </activity>
-      <activity
-        android:name=".LegacyTestActivity"
-        android:label="Legacy Rive Test"
-        android:exported="true"
-        android:theme="@style/AppTheme">
-      </activity>
     </application>
 </manifest>