fix: use package-wide exclusion for JavaScript components in CI

Changed from individual target exclusions to excluding entire //examples/js_component/... package.
This ensures all JavaScript components with ES module resolution issues are excluded from CI build.

Working JavaScript components will be tested in a separate CI step to validate hermetic toolchain.

Author: avrabe

.github/workflows/ci.yml

@@ -133,9 +133,7 @@ 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:hello_js_component \
-            -//examples/js_component:calc_js_component \
-            -//examples/js_component:hello_js_bindings
+            -//examples/js_component/...
 
       - name: Run Tests
         run: bazel test --test_output=errors -- //test/integration:basic_component_build_test //test/integration:basic_component_validation //test/unit:unit_tests