[SDK-115] Wire ci=true instrumentation arg + setAllowedProtocols(\"tester\")

Two small infra pieces that every BCIT test needs:

- run-e2e.sh now passes `ci=true` as an instrumentation argument so
  tests can detect CI mode via InstrumentationRegistry.getArguments().
  Env vars don't reach the test JVM through `am instrument`, so the
  arg is the only reliable channel.
- BaseIntegrationTest.initializeIterableSDK now adds `tester` to
  IterableConfig.allowedProtocols. BCIT campaigns use `tester://` deep
  links; without this the SDK silently drops the URL before invoking
  the URL handler. Matches iOS's
  `config.allowedProtocols = ["tester", "https", "http"]`.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Author: franco-zalamena-iterable

.github/scripts/run-e2e.sh

@@ -110,6 +110,7 @@ trap capture_post_test EXIT
 gradle_exit=0
 ./gradlew :integration-tests:connectedDebugAndroidTest \
   -Pandroid.testInstrumentationRunnerArguments.package="$TEST_PACKAGE" \
+  -Pandroid.testInstrumentationRunnerArguments.ci=true \
   --stacktrace --no-daemon || gradle_exit=$?
 
 if [[ "$gradle_exit" -ne 0 ]]; then

integration-tests/src/androidTest/java/com/iterable/integration/tests/BaseIntegrationTest.kt

@@ -109,6 +109,8 @@ abstract class BaseIntegrationTest {
             .setEnableEmbeddedMessaging(true)
             .setLogLevel(Log.VERBOSE)
             .setInAppDisplayInterval(3.0)
+            // Match the iOS BCIT app: BCIT campaigns use `tester://` deep links.
+            .setAllowedProtocols(arrayOf("tester", "https", "http"))
             .setInAppHandler { message ->
                 // Handle in-app messages during tests
                 Log.d("BaseIntegrationTest", "In-app message received: ${message.messageId}")