Should we revert PreviewDevice (and associated code)? #162693
Description
I am working on a totally unrelated set of features in #162649.
As part of this, I noticed that <FlutterCommand>.verifyThenRunCommand always checks for "allowed plugins":
flutter/packages/flutter_tools/lib/src/runner/flutter_command.dart
Lines 1897 to 1904 in f5e8fc3
This is problematic, today regeneratePlatformSpecificTooling is called once (implicitly when --no-pub is omitted), even on so-called "meta builds" such as flutter build aar or flutter build ios-framework which, by default, build debug, profile, and release mode builds.
With an upcoming change (--explicit-pacakge-dependencies), we need to inform regeneratePlatformSpecificTooling what the current build mode is. So, this code to regenerate platform specific tooling needs to be run differently for meta-builds. @andrewkolos mentioned this project is on indefinite hiatus, so if so, should we revert/remove the associated code (it can always be restored via Git-foo in the future)?
@christopherfujino assigning to you - if you are OK with this revert, LMK, otherwise we can chat further.