feat: make the Ivy compiler the default for ngc (#32219)

This commit switches the default value of the enableIvy flag to true.
Applications that run ngc will now by default receive an Ivy build!

This does not affect the way Bazel builds in the Angular repo work, since
those are still switched based on the value of the --define=compile flag.
Additionally, projects using @angular/bazel still use View Engine builds
by default.

Since most of the Angular repo tests are still written against View Engine
(particularly because we still publish VE packages to NPM), this switch
also requires lots of `enableIvy: false` flags in tsconfigs throughout the
repo.

Congrats to the team for reaching this milestone!

PR Close #32219

packages/compiler-cli/integrationtest/flat_module/tsconfig-build.json

@@ -2,7 +2,8 @@
   "angularCompilerOptions": {
     "flatModuleId": "flat_module",
     "flatModuleOutFile": "index.js",
-    "skipTemplateCodegen": true
+    "skipTemplateCodegen": true,
+    "enableIvy": false
   },
 
   "compilerOptions": {

packages/compiler-cli/integrationtest/ngtools_src/tsconfig-build.json

@@ -1,6 +1,7 @@
 {
   "angularCompilerOptions": {
-    "debug": true
+    "debug": true,
+    "enableIvy": false
   },
 
   "compilerOptions": {

packages/compiler-cli/integrationtest/third_party_src/tsconfig-build.json

@@ -1,6 +1,7 @@
 {
   "angularCompilerOptions": {
-    "skipTemplateCodegen": true
+    "skipTemplateCodegen": true,
+    "enableIvy": false
   },
 
   "compilerOptions": {

packages/compiler-cli/integrationtest/tsconfig-build.json

@@ -4,7 +4,8 @@
     "annotationsAs": "static fields",
     "debug": true,
     "enableSummariesForJit": true,
-    "i18nFormat": "xlf"
+    "i18nFormat": "xlf",
+    "enableIvy": false
   },
 
   "compilerOptions": {

packages/compiler-cli/integrationtest/tsconfig-xi18n.json

@@ -1,7 +1,8 @@
 {
   "angularCompilerOptions": {
     "debug": true,
-    "enableSummariesForJit": true
+    "enableSummariesForJit": true,
+    "enableIvy": false
   },
 
   "compilerOptions": {