Support verbose logging for third-party tools

[rmartin16]

Changes

• Ensure the name of distributable debug APKs have a different file name than release APKs.
• Verbose tool logging is now enabled with -vv
• Gradle builds
  • Enable (very verbose) debug logging via --debug
• linuxdeploy builds
  • Set DEBUG=1 for plugin debug logging
  • Pass -v0 to linuxdeploy for debug logging
• iOS
  • xcodebuild now runs with -verbose
• Flatpak
  • Calls to flatpak and flatpak-builder use --verbose
• macOS Xcode
  • xcodebuild now runs with -verbose
• Visual Studio
  • Runs MSBuild with -verbosity:detailed

Notes

• Linux System package builds
  • Evaluated verbose logging for package builds....but there wasn't much value there
• ADB commands
  • ADB_TRACE=all can increase logging...but it breaks output parsing so omitted
  • If there's potential value here, I can look more deeply at this
• RCEdit
  • Doesn't seem to support additional logging....not sure if value anyway
• WiX
  • Verbose logging doesn't seem to add any value...mostly very cryptic messages from light.exe

PR Checklist:

• All new features have been tested
• All new features have been documented
• I have read the CONTRIBUTING.md file
• I will abide by the code of conduct

[rmartin16]

Adding to its own post to make sure it's clear (and acceptable): as part of the readability refactoring I did for APK/AAB handling, I changed the extension for the Debug APK to be .debug.apk so it doesn't collide with the Release APK extension .apk.

[freakboy3742]

Looks good to me. I've made one additional tweak, correcting the "count" of verbosity. For some reason, not specifying verbosity returned a count of 1, -v was a count of 2, and -vv was 3. To avoid future confusion, I've made the count match the number of v's.