[Tooling] Improve the Installable Build comment

[AliSoftware]

Why

There were some confusion about Google Login not working on Installable Builds recently, so we want to better communicate those limitations (and other info) about Installable Builds

What

This improves the Installable Build PR comment done by CI on our PRs to:

• Hide the QR code under a collapsible section, to reduce noise on the PR
• Use the collapsible section and the fact that we have some room at the right of the QR code to add some more metadata there, including product flavor, and commit to build it (especially useful when you push new commits after a first installable build has been done, to check if the comment is about the old or new commit)
• Add information about the limitations of those installable builds around Google Login (because the appID used by JalapanoDebug builds isn't whitelisted in our Firebase config at the moment — and we don't have much slots left in there to add it anyway)

[Internal ref: pdnsEh-BN-p2]

To test

Just check the look of the Installable Build comment posted by CI on this very PR.

This is how it should look like (for WordPress), collapsed by default:

And how it should look like (for Jetpack) once you manually expand the triangle:

[wpmobilebot]

📲 You can test these changes on WordPress by downloading wordpress-installable-build-pr17199-bd865c2.apk

	💡 Scan this QR code with your Android phone to download and install the APK directly on it.
	App	WordPress
	Build Flavor	Jalapeno
	Build Type	Debug
	Commit	bd865c2

Note: This installable build uses the JalapenoDebug build flavor, and does not support Google Login.

[wpmobilebot]

📲 You can test these changes on Jetpack by downloading jetpack-installable-build-pr17199-bd865c2.apk

	💡 Scan this QR code with your Android phone to download and install the APK directly on it.
	App	Jetpack
	Build Flavor	Jalapeno
	Build Type	Debug
	Commit	bd865c2

Note: This installable build uses the JalapenoDebug build flavor, and does not support Google Login.

[AliSoftware]

PS: @antonis I've added you as reviewer since you're the one who opened #17147. So feel free to tell if you find this new wording and presentation better and if it would solve the confusion you had about Google Login earlier this month 🙂

[antonis]

Great work @AliSoftware 👍
The changes in the PR comments make things a lot clearer 🥇
The code changes also look consistent to me 🎉

[ParaskP7]

👋 @AliSoftware !

I reviewed and tested this PR as per the description, everything LGTM, I really love this change! 🌟 ❤️ 🥇

I have left a couple of naming related suggestion (💡) for you. I am approving this PR anyway. However, I am not merging this PR in case you would like to apply any of those suggestions.

[ParaskP7]

Awesome, thank you so much for addressing my feedback @AliSoftware , everything LGTM! 🚀