This broke the Fuchsia build.

This reverts commit 45e1ad27.

000cf0560c clean up type_literal_test
0f20911022 Improve type_literal_test
a108bef7fb [vm, bytecode] Interpreter support for newer recognized natives.
2a15d38759 Revert "[llvm] Add initial scaffolding"
13b470ac46 Parse error expectations in tests.
b71d2d9996 [llvm] Add initial scaffolding
5f2bcd9d6c [vm/bytecode] Reuse flow graph building for recognized methods

This includes a breaking change: https://dart-review.googlesource.com/c/sdk/+/105241
```
  Dart_CreateIsolate -> Dart_CreateIsolateGroup
  Dart_IsolateCreateCallback -> Dart_IsolateGroupCreateCallback
  Dart_IsolateCleanupCallback -> Dart_IsolateGroupShutdownCallback
  Dart_CreateIsolateFromKernel -> Dart_CreateIsolateGroupFromKernel
  Dart_CurrentIsolateData -> Dart_CurrentIsolateGroupData
  Dart_IsolateData -> Dart_IsolateGroupData
  Dart_GetNativeIsolateData -> Dart_GetNativeIsolateGroupData
  Dart_InitializeParams.create -> Dart_InitializeParams.create_group
  Dart_InitializeParams.cleanup -> Dart_InitializeParams.shutdown_group
  Dart_InitializeParams.shutdown -> Dart_InitializeParams.shutdown_isolate
```

Adds --observatory-host, which allows callers to specify the localhost
IP binding directly. Allows users to set 0.0.0.0 or the host IP address
as is possible in the standalone VM, rather than restricting users to
loopback.

We retain the default behaviour of binding to loopback since the vast
majority of observatory use-cases involve local access (e.g. host tests
on flutter_tester) or port-forwarded local access (e.g. flutter driver
device tests). However, some scenarios, such as QA test labs, may
benefit from binding to a publicly-accessible IP address.

Applications can use an embedder API to obtain the isolate ID and then use it
in calls to the Dart service protocol.

* Revert "[fuchsia] Fix alignment of Fuchsia/non-Fuchsia tracing (#9289)"

This reverts commit f80ac5f5.

* Revert "Align fuchsia and non-fuchsia tracing (#9199)"

This reverts commit 78265484.

The sticky error may be set in cases such as an unhandled asynchronous
exception.  This is similar to the logging done in the Dart command line
embedder's isolate shutdown callback.

The callbacks can be wired in via the Settings object. Both runtime and shell unit-tests have been patched to test this.

This reverts commit 0fcfa0df.
Windows depends on referencing the snapshot symbols directly instead of
via dlsym. Something in the way these symbolsa are generated in
bin_to_assembly.py is causing them to be inaccessible at runtime.

This reverts commit 905ddb6c.

Fixes https://github.com/flutter/flutter/issues/26782.

These are now shutdown by the VM and cleanup waits for their shutdown.

Some components in the Flutter engine were derived from the forked blink codebase. While the forked components have either been removed or rewritten, the use of the blink namespace has mostly (and inconsistently) remained. This renames the blink namesapce to flutter for consistency. There are no functional changes in this patch.

This reverts commit 800ea0a4.

This reverts commit b59c4436.

Revert "Revert "Separate the data required to bootstrap the VM into its own class. (#8397)" (#8406)" (#8414)

This reverts commit f7b4903d.

This reverts commit c9916474.

When attempting to shutdown and subsequently restart the VM, having the
VM own this data introduces lifecycle issues due to circular references.

* Fixed service isolate not being initialized correctly due to bad name

The name for the service isolate was being set to the empty string,
causing the microtask loop to not be run on the service isolate leading
to the service hanging on the first 'await'. See
https://dart-review.googlesource.com/c/sdk/+/97107 for revert due to
this issue.

* Removed unnecessary params from DartCreateAndStartServiceIsolate

This reverts commit 0d6ff166.

The shell was already designed to cleanly shut down the VM but it couldnt
earlier as |Dart_Initialize| could never be called after a |Dart_Cleanup|. This
meant that shutting down an engine instance could not shut down the VM to save
memory because newly created engines in the process after that point couldn't
restart the VM. There can only be one VM running in a process at a time.

This patch separate the previous DartVM object into one that references a
running instance of the DartVM and a set of immutable dependencies that
components can reference even as the VM is shutting down.

Unit tests have been added to assert that non-overlapping engine launches use
difference VM instances.

Re-land "Wrap the user entrypoint function in a zone with native exception callback. (#7512)" (#7551)

This reverts commit 4c135c29 and applies relevant fixes.

Revert "Wrap the user entrypoint function in a zone with native exception callback. (#7512)" (#7522)

This reverts commit 25559ed0.

Reason for revert: broken in AOT mode.

@pragma('vm:entry-point') placed on a function only instructs
the compiler to retain the function itself, but does not tell
compiler to generate and retain tear-off for this function.

In this PR _runMainZoned was marked as an entry-point but C++
code was trying to tear it off and use a closure, instead of
invoking it directly, which is not supported.

This PR prepares Flutter engine for the cleanup of Dart API Dart_GetStickyError/Dart_SetStickyError/Dart_HasStickyError.

* Make IOManager own resource context

* Set up secondary isolates with all kernel buffers rather than just one buffer.
* Capture copy of the list
* Make sure child_isolate_preparer_ is initialized only once

TL;DR: Offscreen surface is created on the render thread and device to host
transfer performed there before task completion on the UI thread.

While attempting to snapshot layer trees, the engine was attempting to use the
IO thread context. The reasoning was that this would be safe to do because any
textures uploaded to the GPU as a result of async texture upload would have
originated from this context and hence the handles would be valid in either
context. As it turns out, while the handles are valid, Skia does not support
this use-case because cross-context images transfer ownership of the image from
one context to another. So, when we made the hop from the UI thread to the IO
thread (for snapshotting), if either the UI or GPU threads released the last
reference to the texture backed image, the image would be invalid. This led to
such images being absent from the layer tree snapshot.

Simply referencing the images as they are being used on the IO thread is not
sufficient because accessing images on one context after their ownership has
already been transferred to another is not safe behavior (from Skia's
perspective, the handles are still valid in the sharegroup).

To work around these issues, it was decided that an offscreen render target
would be created on the render thread. The color attachment of this render
target could then be transferred as a cross context image to the IO thread for
the device to host tranfer.

Again, this is currently not quite possible because the only way to create
cross context images is from encoded data. Till Skia exposes the functionality
to create cross-context images from textures in one context, we do a device to
host transfer on the GPU thread. The side effect of this is that this is now
part of the frame workload (image compression, which dominate the wall time,
is still done of the IO thread).

A minor side effect of this patch is that the GPU latch needs to be waited on
before the UI thread tasks can be completed before shell initialization.

Fixes https://github.com/flutter/flutter/issues/22478

* Roll Dart to version 7f9a9feae181573cca609fd1b8760d7992176699

This contains the following commits:

7f9a9feae1 [vm, service] Rename 'invoke' parameter 'receiverId' to 'targetId'.
fa3d8fa567 Don't check for the file presence in transitive sets when we are just creating it.
6f3de544ed [ VM / Hot Reload ] Fixed tests which were crashing periodically. Fixes issue #34599
e811b29788 [vm, gc] Restore growth policy when concurrent marking is not enabled.
0518b334ba Address comments
7c46a28505 Update convert class to mixin assist to remove "abstract"
06744c68b2 Pull reporting for unimplemented inherited members, and declared abstract members from ErrorVerifier.
45c7e4365c Update dartfix to apply changes to file rather than displaying them
9ad59bada2 [dartdevc] fix #34358, int to double conversion for literals
edddc0ba58 Generate source changes for converting class to mixin
2742a5d558 [Gardening] Update test status
d9de98e164 [VM] Delete some dead code in gen_snapshot.cc
51b8fc7bb0 AwaitExpression.precedence => 14
2390b3605f Create a package for shared diagnostics
629d76eb46 Simple dartfix that suggests class to be converted to mixins
8a2cfd8613 Implement InheritanceManager2.getMember() and use it in some places.
71eaf3209b Fix broken 'fasta testing sdk'.
d79f7493b3 Test that type parameters of typedefs are properly bounds checked.
b36f4fffc4 Allow multiple analyzer codes
82b3501c3c Fix supermixin handling in dart2js
c9b05d3f1f Allow super calls in mixin declarations
225b8d5075 Specialize Object properties in static type computation
4a58112a7c Move kernel_impact.dart from ssa/ to kernel/
aaf3b709e6 [release] Prepare changelog for 2.1.0-dev.6.0
e9c949372e Remove unused parts of J/K*Env classes
4659cb9480 Fully split JsToElementMap and KernelToElementMap
a617700b17 Removes code that has become redundant since 98a9adf.
7c54fab8a5 Adjust status files.
76470aca47 [VM] use coresnapshot when initializing an Isolate

* Address review comments.

Following fixes in dart-lang/sdk@91cbb57cd5cd012d5aa66bfb6eb3a1306271f431