fix: use specific JavaScript component exclusions in CI

Replace wildcard exclusion with specific target exclusions for problematic
multi-file JavaScript components. This ensures that:

- hello_js_component (multi-file: index.js + utils.js) is excluded
- calc_js_component (multi-file: calculator.js + types.js) is excluded
- hello_js_bindings (transpilation target) is excluded
- simple_js_component (single-file: simple.js) can still be built

This more precise exclusion prevents Bazel from attempting to build
components with known module resolution issues while allowing
well-functioning single-file components to be tested.

Author: avrabe

.github/workflows/ci.yml

@@ -133,7 +133,9 @@ jobs:
             -//test/unit:test_component_with_deps_wasm_lib_release_host \
             -//examples/basic:hello_component_wasm_lib_release_host \
             -//tools/checksum_updater_wasm:checksum_updater_wasm_wizer_component_release_wasm_lib_release_host \
-            -//examples/js_component/... \
+            -//examples/js_component:hello_js_component \
+            -//examples/js_component:calc_js_component \
+            -//examples/js_component:hello_js_bindings \
             -//test/js/...
 
       - name: Run Tests