fix: remove 'tools' parameter from file_ops actions to enable runfiles

When a binary is passed as 'executable' in ctx.actions.run(), Bazel
automatically provides runfiles support. However, also passing it in the
'tools' parameter prevents runfiles from being properly initialized in
the sandbox.

Remove the 'tools = [file_ops_tool]' parameter from both:
- prepare_workspace_action() / PrepareWorkspaceHermetic action
- setup_js_workspace_action() / SetupJSWorkspace action

This allows the file_ops binary to properly initialize its runfiles
and locate its data dependencies (wasmtime binary, WASM components, etc.)

Fixes: "Failed to initialize runfiles: runfiles: no runfiles found" error

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

Author: avrabe

tools/bazel_helpers/file_ops_actions.bzl

@@ -231,7 +231,6 @@ def prepare_workspace_action(ctx, config):
             config.get("workspace_type", "generic"),
             ctx.label,
         ),
-        tools = [file_ops_tool],
     )
 
     return workspace_dir
@@ -458,7 +457,6 @@ def setup_js_workspace_action(ctx, sources, package_json = None, npm_deps = None
         outputs = [workspace_dir],
         mnemonic = "SetupJSWorkspace",
         progress_message = "Setting up JavaScript workspace for %s" % ctx.label,
-        tools = [file_ops_tool],
     )
 
     return workspace_dir