Fix #1047 Bump targetSdkVersion to 36

[Ubeydu]

Google Play requires apps to target Android 16 (API 36) from Aug 31, 2026 (#1047).

Main already compiles against SDK 36: e0af5ad bumped compileSdkVersion to 36 together with AGP 8.9.1, Gradle 8.11.1 and JDK 17. This PR completes the move for generated apps:

• packages/core/template_project/app/build.gradle: bumps targetSdkVersion from 35 to 36
• packages/core/src/lib/androidSdk/AndroidSdkTools.ts: bumps BUILD_TOOLS_VERSION from 34.0.0 to 36.1.0 (latest stable 36.x, same pairing as Fix #750 Bump compileSdkVersion and targetSdkVersion to 33 #764 and Support Android SDK version 35, with many consequential updates #862; the specs interpolate the constant, so no test changes are needed)

Note: this overlaps with #1050 on the template line; that PR was opened while I was validating this branch end to end. The addition here is the BUILD_TOOLS_VERSION pairing from #764 and #862 (see 39d5972), plus the verification below. If the minimal shape of #1050 is preferred, I am happy to rebase this down to the build-tools companion change.

Verification, all done with this branch:

• npm ci, build, lint and test: green on all three packages.
• Generated the TWA for my production PWA (com.akluma.app, currently in closed testing on Google Play) with the patched CLI: the generated project gets targetSdkVersion 36, and bubblewrap build installed build-tools;36.1.0 from scratch via sdkmanager on a clean SDK, confirming the version string resolves.
• The built APK verifies: aapt2 badging reports targetSdkVersion 36, signed with the app's existing upload key.
• Installed and ran on an Android 16 (API 36) emulator: the TWA launches full screen with Digital Asset Links verification working (no URL bar). Screenshot below.

I will upload the AAB to Google Play in the coming days and report acceptance here.

Out of scope, noted for the record: bumping android-browser-helper past 2.6.2 (the edge-to-edge splash fixes landed in 2.7.x) raises the library minSdk from 21 to 23, a breaking change that deserves its own PR. Same for the Play Billing Library 8.0 question raised in #1047, which lives in android-browser-helper's billing module.

[Ubeydu]

Real-world confirmation: Google Play today accepted and published a bundle built with this change applied (targetSdkVersion 36, build tools 36.1.0). The Play Console reads the bundle as target SDK 36, and it went live on my app's closed testing track with no warnings.

[ghnp5]

Hey! Do you confirm that this change is really included in the last release?

When I use the latest Docker container (ghcr.io/googlechromelabs/bubblewrap:latest, after pulling it),
and then run bubblewrap init,

the result is still targetSdkVersion 35 in build.gradle.

I know I can update it manually, but I was expecting bubblewrap to do it for me.

Thanks!

[ghnp5]

Maybe this is the reason: pwa-builder/PWABuilder#6159 (comment)

But that means that whenever the NPM version is released, the docker image needs to be updated too, so it can pull the latest npm package.