build: Google Play deploy to internal

[VaiTon]

Deploy to internal track on Google Play every night at 00:00 UTC or on manual trigger.

Also renamed closed_beta in fastfile to internal to better reflect where the deployment is made.

Related to

• Release policy #2249 (comment)

[g123k]

I wonder what's the best deployment scenario.
My personal preference is to have two apps: Smoothie (for tests) and OFF (stable).

@VaiTon Do your changes still allow this mechanism?

[VaiTon]

Hey @g123k !

My personal preference is to have two apps: Smoothie (for tests) and OFF (stable).

If you're on the internal branch team the app would update every night, so no two versions. But I wonder if that is possible with the current configuration. How do you manage to do it?

[teolemon]

Run flutter analyze --fatal-infos --fatal-warnings .
Analyzing smooth-app...

error • The body might complete normally, causing 'null' to be returned, but the return type, 'Widget', is a potentially non-nullable type • packages/smooth_app/lib/knowledge_panel/knowledge_panels/knowledge_panel_element_card.dart:24:10 • body_might_complete_normally
warning • Missing case clause for 'ACTION' • packages/smooth_app/lib/knowledge_panel/knowledge_panels/knowledge_panel_element_card.dart:25:5 • missing_enum_constant_in_switch

2 issues found. (ran in 29.0s)
Error: Process completed with exit code 1.

[M123-dev]

Fixed by #2983