test(ivy): mark failing test targets with fixme-ivy-jit and fixme-ivy-local tags (#26471)

We are close enough to blacklist a few test targets, rather than whitelist targets to run...

Because bazel rules can be composed of other rules that don't inherit tags automatically,
I had to explicitly mark all of our ts_library and ng_module targes with "ivy-local" and
"ivy-jit" tags so that we can create a query that excludes all fixme- tagged targets even
if those targets are composed of other targets that don't inherit this tag.

This is the updated overview of ivy related bazel tags:

- ivy-only: target that builds or runs only under ivy
- fixme-ivy-jit: target that doesn't yet build or run under ivy with --compile=jit
- fixme-ivy-local: target that doesn't yet build or run under ivy with --compile=local
- no-ivy-jit: target that is not intended to build or run under ivy with --compile=jit
- no-ivy-local: target that is not intended to build or run under ivy with --compile=local

PR Close #26471

packages/bazel/test/protractor-2/BUILD.bazel

@@ -8,8 +8,6 @@ ts_library(
     name = "app",
     srcs = ["app.ts"],
     tsconfig = ":tsconfig.json",
-    # FIXME: should not be needed here!
-    deps = ["@ngdeps//@types/jasmine"],
 )
 
 ts_devserver(
@@ -37,7 +35,7 @@ ts_library(
     name = "ts_spec",
     testonly = True,
     srcs = ["test.spec.ts"],
-    tsconfig = ":tsconfig.json",
+    tsconfig = ":tsconfig.test.json",
     deps = [
         "@ngdeps//@types/selenium-webdriver",
         "@ngdeps//protractor",

packages/bazel/test/protractor-2/tsconfig.json

@@ -1,6 +1,6 @@
 {
   "compilerOptions": {
     "lib": ["dom", "es2015"],
-    "types": ["jasmine"]
+    "types": []
   }
 }

packages/bazel/test/protractor-2/tsconfig.test.json

@@ -0,0 +1,6 @@
+{
+  "extends": "./tsconfig.json",
+  "compilerOptions": {
+    "types": ["jasmine"]
+  }
+}