Implementing switch expressions in flutter_tools/

[nate-thegrate]

This pull request is step 12 in the journey to make this entire repository more readable.

(previous PRs: #139048, #139882, #141591, #142279, #142634, #142793, #143293, #143496, #143634, #143812, #144580)

We're getting close to the end! 😄

[gspencergoog]

Thanks, these look a lot nicer!

[loic-sharma]

Looks great, thanks!

[kevmoo]

This could/should be deprecated and usages should just use name!

[kevmoo]

could just have the success -> installed bit and then a default to using name

[gspencergoog]

Won't the default make it so that the lint about not using all of the enum values doesn't fire if a new enum value is added (which could have a type name that doesn't match the enum name). Without the default, the lint will require considering this switch when one is added.

[nate-thegrate]

Yep, it would clean things up nicely, but it would also break that style guideline.

But I think it's possible to get rid of the switch expression altogether:

enumValidationType {
crash,
missing,
partial,
notAvailable,
success('installed');
constValidationType([this.label]);
finalString? label;
@overrideStringtoString() => label ?? name;
}