Relax strictness of mocks in DisplayLayoutTests

- The mocking of the resources includes resource values that
  aren't currently tested, but should be mocked to be consistent
  with the other values.  We should treat these as warnings and
  not a test blocker (might be a difference in the version of
  mockito used in studio dev)

Bug: 239892577
Test: Run WMShellUnitTests from sysui studio
Change-Id: I03594b6fb0889f29124882a1f61d7b94b4f90b55

libs/WindowManager/Shell/tests/unittest/src/com/android/wm/shell/common/DisplayLayoutTest.java

@@ -47,6 +47,7 @@ import org.junit.After;
 import org.junit.Before;
 import org.junit.Test;
 import org.mockito.MockitoSession;
+import org.mockito.quality.Strictness;
 
 /**
  * Tests for {@link DisplayLayout}.
@@ -62,6 +63,7 @@ public class DisplayLayoutTest extends ShellTestCase {
     public void setup() {
         mMockitoSession = mockitoSession()
                 .initMocks(this)
+                .strictness(Strictness.WARN)
                 .mockStatic(SystemBarUtils.class)
                 .startMocking();
     }