build: update instructions to run benchmark tests (#28645)

* Updates the instructions on how to run the benchmark tests.
* Removes the unused `favicon.ico` file and the corresponding Bazel filegroup

PR Close #28645

modules/benchmarks/BUILD.bazel

@@ -5,10 +5,3 @@ exports_files([
     "tsconfig-e2e.json",
     "start-server.js",
 ])
-
-filegroup(
-    name = "favicon",
-    srcs = [
-        "favicon.ico",
-    ],
-)

modules/benchmarks/README.md

@@ -3,39 +3,23 @@
 ## Run in the browser
 
 ```bash
-# Build the Angular packages.
-yarn tsc -p packages/
+yarn bazel run modules/benchmarks/src/tree/{name}:devserver
 
-# Build the e2e tests which are part of the "modules/"
-./modules/build.sh
-
-# Start server that serves all benchmark e2e apps.
-yarn gulp serve
-```
-
-Now you can open benchmark e2e apps using their appropriate URLs. For example:
-
-```
-http://localhost:8000/all/benchmarks/src/tree/ng2/index.html
+# e.g. "ng2" tree benchmark:
+yarn bazel run modules/benchmarks/src/tree/ng2:devserver
 ```
 
 ## Run e2e tests
-$ export NODE_PATH=$(pwd)/dist/all:$(pwd)/dist/tools
-$ ./node_modules/.bin/protractor protractor-e2e.conf.js --specs=dist/all/benchmarks/e2e_test/tree_spec.js
 
-Options for protractor with `protractor-e2e.conf.js`:
-- `--bundles=true`: use prebuilt bundles
-- `--ng-help`: show all available options
+```
+# Run e2e tests of individual applications:
+yarn bazel test modules/benchmarks/src/tree/ng2/...
 
-## Run benchmarks tests
-$ export NODE_PATH=$(pwd)/dist/all:$(pwd)/dist/tools
-$ ./node_modules/.bin/protractor protractor-perf.conf.js --specs=dist/all/benchmarks/e2e_test/tree_perf.js
+# Run all e2e tests:
+yarn bazel test modules/benchmarks/...
+```
 
-Options for protractor with `protractor-perf.conf.js`:
-- `--bundles=true`: use prebuilt bundles
-- `--ng-help`: show all available options
+## Use of *_aot.ts files
 
-## Compile *_aot.ts files
-
-These files are compiled as part of the compiler_cli integration tests.
-See `@angular/compile_cli/integrationtest/tsconfig.json`
+The `*_aot.ts` files are used as entry-points within Google to run the benchmark
+tests. These are still built as part of the corresponding `ng_module` rule.