ci(release): Use wildcards for APK paths in release workflow

[jamesarich]

This commit updates the release.yml GitHub Actions workflow to use wildcards for APK file paths.

Previously, the workflow used explicit filenames like app-google-release.apk. This has been changed to *.apk to make the build process more resilient to changes in APK naming conventions, such as the inclusion of version numbers in the filename.

This modification applies to the artifact upload and provenance attestation steps for both the Google and F-Droid release jobs.

[codecov]

❌ 1 Tests Failed:

Tests completed	Failed	Passed	Skipped
340	1	339	0

View the top 1 failed test(s) by shortest run time

org.meshtastic.feature.firmware.ota.BleOtaTransportErrorTest::streamFirmware fails on hash mismatch at verification

Stack Traces | 0.141s run time

java.lang.IllegalStateException: Peripheral not connected
	at no.nordicsemi.kotlin.ble.client.mock.PeripheralSpec.estimateTransferDuration-3nIYWDw$client_core_mock(PeripheralSpec.kt:275)
	at no.nordicsemi.kotlin.ble.client.mock.PeripheralSpec$simulateValueUpdate$1.invokeSuspend(PeripheralSpec.kt:535)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:34)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:100)
	at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:124)
	at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:89)
	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:586)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:820)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:717)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:704)

To view more test analytics, go to the Test Analytics Dashboard
_{📋 Got 3 mins? Take this short survey to help us improve Test Analytics.}