This PR fixes #594 (comment)

Changes influence only builds when main Gradle template patching is enabled.

Changes:

• Added "Patch settingsTemplate.gradle" checkbox in Android Resolver settings.
• Implemented repositories injection in settingsTemplate.gradle
• Added /resolve/gradlesettingstemplate report URL to the analytics. (Not sure if it is needed)

The logic of repositories injection depends on the project state:

• Project state when mainTemplate.gradle and settingsTemplate.gradle are enabled and mainTemplate patching and settingsTemplate patching in Android Resolver settings are enabled:
  1. Android Resolver will check if settingsTemplate.gradle contains dependencyResolutionManagement block with RepositoriesMode.PREFER_SETTINGS or RepositoriesMode.FAIL_ON_PROJECT_REPOS. If the match is successful it would mean that Gradle is configured to read repositories from settingsTemplate.gradle and will not read repositories specified in mainTemplate.gradle.
  2. If the previous check is successful then Android Resolver will inject repositories in settingsTemplate.gradle before dependencyResolutionManagement line. Injected repositories are in separate dependencyResolutionManagement block and look like this:

  // Android Resolver Repos Start
  dependencyResolutionManagement {
   repositories {
   def unityProjectPath = $/file:///**DIR_UNITYPROJECT**/$.replace("\\", "/")
   maven {
   url "https://maven.google.com"
   }
   maven {
   url "https://maven.google.com/" // Assets/GoogleMobileAds/Editor/GoogleMobileAdsDependencies.xml:7, Assets/GoogleMobileAds/Editor/GoogleMobileAdsDependencies.xml:12, Assets/GoogleMobileAds/Editor/GoogleMobileAdsDependencies.xml:17, Assets/GoogleMobileAds/Editor/GoogleUmpDependencies.xml:7
   }
   mavenLocal()
   mavenCentral()
   }
  }
  // Android Resolver Repos End
  

  3. If the previous check isn't successful then Android Resolver will inject repositories the same way as it is doing in older versions in mainTemplate.gradle
• In the project state when mainTemplate.gradle and settingsTemplate.gradle are enabled and mainTemplate patching is enabled but settingsTemplate patching in Android Resolver settings is disabled, Android Resolver will not patch settingsTemplate.gradle this will lead to the build fail and the user will need to manage repositories manually.
• Project state when mainTemplate.gradle is enabled and mainTemplate patching and settingsTemplate patching in Android Resolver settings are enabled but settingsTemplate.gradle is disabled:
  1. If the Unity version is equal to or above 2022年2月10日 Android Resolver will fail and in the error log will be asked to enable the settings template in "Project Settings".
  2. If the Unity version is below 2022年2月10日 then Android Resolver will check if the default settingsTemplate.gradle in PlaybackEngines/AndroidPlayer/Tools/GradleTemplates contains dependencyResolutionManagement block. Effectively this will match any Unity version equal to or above the 2022.2 version because dependencyResolutionManagement was introduced in the 2022.2 version.
     2.1. If the previous check didn't match then Android Resolver will work as in the previous versions.
     2.2. If the previous check is successful then Android Resolver will enable settingsTemplate.gradle automatically (by copying the default template). Decided to do it in such a way because Unity >=2022.2 and <2022年2月10日 uses a settings template for repositories but don't have an option in "Project Settings" to enable a custom settings template. This option appeared only in 2022年2月10日.