Add strict_mode: false

As strict mode is in place, the default strict_mode is now set to true. We are encourage teams to write tests in strict_mode to make tests Bivalent (able to run on device and devicelessly)
For more info on strict mode: go/roboStrictMode

Flag: NONE
Test: atest SystemUiRoboTests, SpaRoboRNGTests, SettingsLibRoboTests, FrameworksServicesRoboTests, BackupFrameworksServicesRoboTests, InputRoboRNGTests
Bug: 334089788
Change-Id: I9827910496af67eab33efddb7c32d8e40b497c13

packages/CredentialManager/wear/robotests/Android.bp

@@ -25,4 +25,5 @@ android_robolectric_test {
     ],
     java_resource_dirs: ["config"],
     upstream: true,
+    strict_mode: false,
 }

packages/SettingsLib/DataStore/tests/Android.bp

@@ -26,4 +26,5 @@ android_robolectric_test {
     instrumentation_for: "SettingsLibDataStoreShell",
     coverage_libs: ["SettingsLibDataStore"],
     upstream: true,
+    strict_mode: false,
 }

packages/SettingsLib/Spa/screenshot/robotests/Android.bp

@@ -71,4 +71,6 @@ android_robolectric_test {
     upstream: true,
     java_resource_dirs: ["config"],
     instrumentation_for: "SpaRoboApp",
+
+    strict_mode: false,
 }

packages/SettingsLib/tests/robotests/Android.bp

@@ -64,6 +64,8 @@ android_robolectric_test {
         timeout: 36000,
     },
     upstream: true,
+
+    strict_mode: false,
 }
 
 java_genrule {

services/robotests/Android.bp

@@ -64,6 +64,8 @@ android_robolectric_test {
     instrumentation_for: "FrameworksServicesLib",
 
     upstream: true,
+
+    strict_mode: false,
 }
 
 filegroup {

services/robotests/backup/Android.bp

@@ -68,4 +68,6 @@ android_robolectric_test {
 
     upstream: true,
 
+    strict_mode: false,
+
 }

tests/InputScreenshotTest/robotests/Android.bp

@@ -69,4 +69,6 @@ android_robolectric_test {
     upstream: true,
     java_resource_dirs: ["config"],
     instrumentation_for: "InputRoboApp",
+
+    strict_mode: false,
 }