security: remove fake credential encryption

[Tednoob17]

Fixes recoverable production credentials (GCP, BrowserStack, SauceLabs) by removing fake AES-256-GCM encryption whose key was derivable from the public org name.

• Delete committed .data credential files and encrypt.ts
• Replace bundled JS with minimal ESM scripts that read credentials from env
• Update action.yml inputs to accept secrets from GitHub Actions
• Mark required inputs and pass them as env vars in composite action steps
• Restore BUILD.bazel targets without encrypted blob references
• Add test verifying no hardcoded keys or encrypted blobs remain

[gemini-code-assist]

Code Review

This pull request refactors the GitHub Actions for Bazel remote execution, BrowserStack, and Sauce Labs to accept credentials directly via action inputs and environment variables, removing the previous embedded encrypted credential files and decryption logic. A new test script, test-credentials.mjs, is also added to verify that no encrypted files or hardcoded crypto constants are reintroduced. Feedback suggests quoting the script paths in the composite action files to prevent word-splitting issues on paths with spaces, and improving the test script to provide a clearer error message if no compiled JS files are found.

[gemini-code-assist]

Quote the script path to prevent word splitting and execution failures if the runner's workspace path contains spaces (e.g., on certain self-hosted runners or Windows environments).

    - run: node "$GITHUB_ACTION_PATH/configure-remote.js"

[gemini-code-assist]

Quote the script path to prevent word splitting and execution failures if the runner's workspace path contains spaces (e.g., on certain self-hosted runners or Windows environments).

    - run: node "$GITHUB_ACTION_PATH/set-browserstack-env.js"

[gemini-code-assist]

Quote the script path to prevent word splitting and execution failures if the runner's workspace path contains spaces (e.g., on certain self-hosted runners or Windows environments).

    - run: node "$GITHUB_ACTION_PATH/set-saucelabs-env.js"

[gemini-code-assist]

If no JS files are found in the action directory, the test will fail with a generic 'No process.env usage found' error. Consider explicitly checking if the JS files array is empty and pushing a more descriptive error message to help developers identify that the build outputs are missing.

[alan-agius4]

Forked repos cannot access secrets, which disables RBE for pull requests and breaks existing workflows.