Declare allowed secret names to allow loading environmental values

The way environment secrets and var work is a bit wonky, but without
these being declared, even though the secrets themselves are defined in
the caller repo's environment, the values were just empty. I don't think
the caller has to explicitly pass them in (as they can't be resolved
without an `environment` delcaration anyway), so I'm hoping just making
them not required will be okay, and we'll leave our actual safety checks
in place to validate that we have something.

Author: elasticdog

.github/workflows/draft-release-flutter.yml

@@ -30,6 +30,25 @@ on:
         required: false
         type: string
         default: upload
+    secrets:
+      ANDROID_APP_SIGNING_KEYSTORE_B64:
+        required: false
+      ANDROID_APP_SIGNING_KEYSTORE_PASSWORD:
+        required: false
+      ANDROID_APP_SIGNING_KEY_PASSWORD:
+        required: false
+      ANDROID_UPLOAD_KEYSTORE_B64:
+        required: false
+      ANDROID_UPLOAD_KEYSTORE_PASSWORD:
+        required: false
+      ANDROID_UPLOAD_KEY_PASSWORD:
+        required: false
+      IOS_SIGNING_CERT_B64:
+        required: false
+      IOS_SIGNING_CERT_PASSWORD:
+        required: false
+      IOS_PROVISIONING_PROFILE_B64:
+        required: false
 
 permissions:
   contents: read

.github/workflows/upload-build-ios.yml

@@ -7,6 +7,9 @@ on:
       release_tag:
         required: true
         type: string
+    secrets:
+      ASC_AUTH_KEY_B64:
+        required: false
 
 jobs:
   upload_build: