* Regenerate _no.arb and _nb.arb from scratch

* Revert no <--> nb synonym logic

* Update prod builders.

This is to make the builders show up in the flutter dashboard.

Bug:
  https://github.com/flutter/flutter/issues/63256

* Add mac and windows bots.

* Fix flaky flag.

* Rename taskName as task_name.

Update prepare_package.dart to use the process_runner package instead having duplicate code. (#62710)

Updates the prepare_package.dart script to use the process_runner package (which is where the ProcessRunner implementation was moved to).

This makes the processing of RawKeyboardEventData.getModifierSide consistent among the platforms.

Before this change, some platforms (Android) didn't handle the case where the "either" flag was set, but no side flag was set (e.g. "shift" was set, but not "shift left"), and instead said that no keys were down by returning null (which was wrong).

Some platforms (Linux, Windows) also returned KeyboardSide.any from getModifierSide, when the contract says that it will never return KeyboardSide.any. Those methods now return KeyboardSide.all in the case where no side is specified, as macOS and Fuchsia already did.

Now, all platforms will return KeyboardSide.all from getModifierSide when it's not clear which side the key was on.

Updated old button references in dev/integration_tests/flutter_gallery ... full_screen_dialog_demo (#63491)

Updated old button references in dev/integration_tests/flutter_gallery ... transformation_demo (#63432)

This adds an assert in RawKeyboard that catches the case where it tries to send a key down event, but (after synchronizing modifiers) there are no keys in keysPressed. This state can occur if the modifier flags are not set properly for the platform.

Also prevents shortcuts attempting to handle a key down when no keys are pressed at the moment (which was causing a crash in release mode).

It now uses the scroll metrics as they stood at the end of the last frame.

It previously used a weird combination of the old extents and the newish position, which led to some weird effects when the position had been changed in expectation of a viewport or content dimension change.

Framework tests got replaced with a new version using shards. This pr is
enabling the new builders in presubmit and removing the old ones.

Bug:
  https://github.com/flutter/flutter/issues/63258
  https://github.com/flutter/flutter/issues/63242
  https://github.com/flutter/flutter/issues/63241