[heap] Remove all leftover uses of v8_enable_atomic_marking_state

This build flag was removed in https://crrev.com/c/3314864.

Bug: v8:12470
Change-Id: I365a1914ff096d07ae41d8bf35150615a9c91736
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3676853
Commit-Queue: Dominik Inführ <dinfuehr@chromium.org>
Reviewed-by: Michael Achenbach <machenbach@chromium.org>
Reviewed-by: Andreas Haas <ahaas@chromium.org>
Cr-Commit-Position: refs/heads/main@{#80968}

bazel/defs.bzl

@@ -493,7 +493,6 @@ def build_config_content(cpu, icu):
         ("target_cpu", cpu),
         ("v8_current_cpu", cpu),
         ("v8_dict_property_const_tracking", "false"),
-        ("v8_enable_atomic_marking_state", "false"),
         ("v8_enable_atomic_object_field_writes", "false"),
         ("v8_enable_concurrent_marking", "false"),
         ("v8_enable_i18n_support", icu),

infra/mb/mb_config.pyl

@@ -725,8 +725,7 @@
       # atomic marking state enabled because that is needed for the concurrent
       # write-barrier used by background compilation.
       'gn_args': 'v8_enable_concurrent_marking=false '
-                 'v8_enable_atomic_object_field_writes=false '
-                 'v8_enable_atomic_marking_state=true ',
+                 'v8_enable_atomic_object_field_writes=false ',
     },
 
     'disable_pgo': {