[fasta] Tweak fasta unit tests setup in anticipation of constant update 2018

- Pass empty environment defines into CompilerOptions - to ensure that
there are no unevaluated constants in the output. VM does not expect
those.
- Include constant table when comparing expectations

Change-Id: I276e8bf8ce1f4f39c63265e4ae2650953649e41f
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/108800
Auto-Submit: Vyacheslav Egorov <[email protected]>
Commit-Queue: Johnni Winther <[email protected]>
Reviewed-by: Johnni Winther <[email protected]>

Author: mraleph

pkg/front_end/lib/src/fasta/testing/kernel_chain.dart

@@ -230,6 +230,7 @@ class MatchExpectation extends Step<Component, Component, MatchContext> {
       printer.writeLibraryFile(library);
       printer.endLine();
     });
+    printer.writeConstantTable(component);
     String actual = "$buffer";
     String binariesPath = relativizeUri(platformBinariesLocation);
     if (binariesPath.endsWith("/dart-sdk/lib/_internal/")) {

pkg/front_end/test/fasta/testing/suite.dart

@@ -262,6 +262,7 @@ class FastaContext extends ChainContext with MatchContext {
           }
           ..sdkRoot = sdk
           ..packagesFileUri = packages
+          ..environmentDefines = {}
           ..experimentalFlags = <ExperimentalFlag, bool>{
             ExperimentalFlag.controlFlowCollections:
                 enableControlFlowCollections,
@@ -353,6 +354,7 @@ class Outline extends Step<TestDescription, Component, FastaContext> {
             }
             errors.writeAll(message.plainTextFormatted, "\n");
           }
+          ..environmentDefines = {}
           ..experimentalFlags = <ExperimentalFlag, bool>{
             ExperimentalFlag.controlFlowCollections:
                 context.enableControlFlowCollections,