[roll] Roll fuchsia Revert "[bazel] Add `no_sdk_workspace` argument to `bazel_action()`."

This reverts commit 7aac7868dbcab77cec265ec802be354ad5b80ba9.

Reason for revert:

This is making every CL fail tests with the following error:

```Ninja build did not converge to no-op.
See: https://fuchsia.dev/fuchsia-src/development/build/ninja_no_op

First line of ninja explain output:

recorded mtime of gen/build/bazel/bazel older than most recent input sdk/exported/bazel_in_tree_idk/meta/manifest.json```

Original change's description:
> [bazel] Add `no_sdk_workspace` argument to `bazel_action()`.
>
> This CL changes `bazel_action()`, `bazel_build_action()` and
> `bazel_build_group()` to support a new `no_sdk_workspace = true`
> argument, which allows invoking Bazel immediately, i.e. before
> building the IDK with Ninja (which is currently required to populate
> the `@fuchsia_sdk` repository, and a few other ones).
>
> This works by leveraging the `--config=no_sdk` introduced in
> a previous CL that overrides the IDK/SDK repository definitions
> with empty/fake ones.
>
> In this mode:
>
> - No Fuchsia-compatible C++ toolchain is available.
>   It is possible to build host C++ binaries.
>
> - No targets using Fuchsia-specific rules from `@rules_fuchsia`
>   will build properly.
>
> - It is still possible to use `@platforms//os:fuchsia` and
>   `@rules_fuchsia//fuchsia/constraints:...` in `select()`
>   statements.
>
> This CL opens the door to moving host tool generation to the
> Bazel graph entirely. A future CL will introduce a new GN
> template `bazel_host_tool()` to make such binaries directly
> usable in the Ninja graph and exported to build archives,
> similar to what `host_tool()` is currently doing.
>
> This also introduces `//:bazel_workspace_no_sdk` which can
> be used to setup the Bazel workspace immediately, then launch
> a Bazel command to build a host binary, for example, after
> `fx clean && fx gen`, the following takes only 6.5 seconds
> on a workstation:
>
> ```
> fx build bazel_workspace_no_sdk &&
> fx bazel run --config=quiet --config=no_sdk //build/bazel/examples/hello_world
> ```
>
> And will print `Hello World from Bazel!` :-)
>
> Alternatively, it is technically possible to setup the Bazel workspace
> without invoking Ninja, after a successful `fx gen` by invoking the
> `update_workspace.py` script directly, however, this requires invoking
> `bazel` directly, instead of using the `fx bazel` wrapper, as in:
>
> ```
> build/bazel/scripts/update_workspace.py
> $(fx get-build-dir)/gen/build/bazel/bazel run --config=quiet --config=no_sdk //build/bazel/examples/hello_world
> ```
>
> Which only takes 4.1 seconds (including building), and only 1.3 seconds
> when re-running a second time (with no source changes).
>
> This feature will be the basis for generating build API files
> from the Bazel graph at `fx gen` time in the future, as it will be possible
> to perform queries over the part of the Bazel graph that doesn't
> define Fuchsia targets.
>
> Change-Id: Ifcfa390cff519a55f7ee097046f95c0fe975c9fa
> Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1164757
> Reviewed-by: Jiaming Li <lijiaming@google.com>
> Reviewed-by: David Fang <fangism@google.com>
> Commit-Queue: Auto-Submit <auto-submit@fuchsia-infra.iam.gserviceaccount.com>
> Fuchsia-Auto-Submit: David Turner <digit@google.com>

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1166374
Original-Revision: b3d6e83c561251c8894850d1135db3cd94222a71
GitOrigin-RevId: 76f7211d75fb37c983e21a635a54c3ba9e434f78
Change-Id: I80fa98ccd59b60f4f0e8ab98486886dae5165d32