Add targetSdk to library modules in the testOptions

[hud10837]

Related to issue: https://devtopia.esri.com/runtime/kotlin/issues/4231

Description:

Tests are failing due to a popup window that says the app was built for an older version of Android. This has to do with some changes that were introduced by https://issuetracker.google.com/issues/230625468. They deprecated targetSdk for library modules, but when the test app is spun up, it doesn't have a targetSdk and seems to default to minSdk. As a fix, you can now supply targetSdk to testOptions, so I've done that in every library gradle file, as well as adding it into the lint blocks for good measure as that was suggested in the google issue.

Summary of changes:

• Add targetSdk to library modules testOptions blocks.
• Add a new flag to successful OAuth sign in tests: FLAG_ACTIVITY_NEW_TASK, which was causing an error and making two tests fail.

Pre-merge Checklist

• a vTest Job for this PR has been run
  • link: https://runtime-kotlin.esri.com/job/vtest/job/toolkit/48/
• Unit and/or integration tests have been added to exercise this PR's logic, and the tests are passing:
  • Yes
  • No

[colinanderson]

@hud10837 changes look like they match the Google issue and the doc I found for FLAG_ACTIVITY_NEW_TASK so looks ok to me.

[TADraeseke]

Nice fix @hud10837! I ran successfulSignIn() test before and after your PR and confirm it doesn't pop up with window about sdk version. Nice one!