Bazel Docs: Remove all DevSite tags from new .mdx docs.

GCLI created a Python script in unknown commit that did all the heavy lifting.

This is a breaking change, but unfortunately Mintlify isn't going to support custom heading IDs in the near future. Workarounds are being tracked in bazel-contrib/bazel-docs#252

Our best course of action is to fix the parsing errors by removing the custom IDs, then proceed with the workarounds.

PiperOrigin-RevId: 879883162
Change-Id: I328765485bf3dacf4118357083488abb796ba2bc

Author: fweikert

docs/community/users.mdx

@@ -51,7 +51,7 @@ ASML is an innovation leader in the semiconductor industry. We provide chipmaker
 with everything they need – hardware, software and services – to mass produce
 patterns on silicon through lithography.
 
-### [Augment Code](https://augmentcode.com){: .external}
+### [Augment Code](https://augmentcode.com)
 
 Augment Code is the first Developer AI for teams.
 Every Augment feature is context aware. Every suggestion, completion, and

docs/concepts/build-files.mdx

@@ -17,7 +17,7 @@ For simplicity's sake, the documentation refers to these files simply as `BUILD`
 files.
 
 `BUILD` files are evaluated using an imperative language,
-[Starlark](https://github.com/bazelbuild/starlark/){: .external}.
+[Starlark](https://github.com/bazelbuild/starlark/).
 
 They are interpreted as a sequential list of statements.
 

docs/contribute/search.mdx

@@ -2,14 +2,14 @@
 title: 'Searching the codebase'
 ---
 
-## Product overview {:#product-overview}
+## Product overview
 
 Bazel's [code search and source browsing interface](https://source.bazel.build)
 is a web-based tool for browsing Bazel source code repositories. You can
 use these features to navigate among different repositories, branches, and
 files. You can also view history, diffs, and blame information.
 
-## Getting started {:#getting-started}
+## Getting started
 
 Note: For the best experience, use the latest version of Chrome, Safari, or
 Firefox.
@@ -29,9 +29,9 @@ commit.
 At the top of the screen is a search box. You can use this box to search for
 specific files and code.
 
-## Working with repositories {:#working-with-repositories}
+## Working with repositories
 
-### Opening a repository {:#opening-a-repository}
+### Opening a repository
 
 To open a repository, click its name from the main screen.
 
@@ -41,11 +41,11 @@ repository and allows you to move quickly to another location such as another
 repository, or another location within a repository, such as a file, branch, or
 commit.
 
-### Switch repositories {:#switch-repositories}
+### Switch repositories
 
 To switch to a different repository, select the repository from the Breadcrumb toolbar.
 
-### View a repository at a specific commit {:#view-a-repository-at-a-specific-commit}
+### View a repository at a specific commit
 
 To view a repository at a specific commit:
 
@@ -56,7 +56,7 @@ To view a repository at a specific commit:
 
 The interface now shows the repository as it existed at that commit.
 
-### Open a branch, commit, or tag {:#open-a-branch-commit-or-tag}
+### Open a branch, commit, or tag
 
 By default, the code search and source browsing interface opens a repository to
 the default branch.  To open a different branch, from the Breadcrumb toolbar,
@@ -72,7 +72,7 @@ branch using a branch name, a tag name, or through a search box.
 *  To search for a branch, commit, or tag, select the corresponding item and
    type a search term in the search box.
 
-## Working with files {:#working-with-files}
+## Working with files
 
 When you select a repository from the main screen, the screen changes to display
 a view of that repository. If a README file exists, its contents appear in the
@@ -90,13 +90,13 @@ three components:
 *  A **File path** box, which displays the name of the current file or folder
    and its corresponding path
 
-### Open a file {:#open-a-file}
+### Open a file
 
 You can open a file by browsing to its directory and selecting it. The view of
 the repository updates to show the contents of the file in the file pane, and
 its location in the repository in the tree pane.
 
-### View file changes {:#view-file-changes}
+### View file changes
 
 To view file changes:
 
@@ -105,15 +105,15 @@ To view file changes:
 
 The file pane updates to display who made changes to the file and when.
 
-### View change history {:#view-change-history}
+### View change history
 
 To view the change history of a file:
 
 1.  From the view of the repository, select the file.
 1.  Click **HISTORY**, located in the upper-right corner.
     The **Change history** pane appears, showing the commits for this file.
 
-### View code reviews {:#view-code-reviews}
+### View code reviews
 
 For Gerrit code reviews, you can open the tool directly from the Change History pane.
 
@@ -128,7 +128,7 @@ To view the code review for a file:
 
 The Gerrit Code Review tool opens in a new browser window.
 
-### Open a file at a specific commit {:#open-a-file-at-a-specific-commit}
+### Open a file at a specific commit
 
 To open a file at a specific commit:
 
@@ -138,7 +138,7 @@ To open a file at a specific commit:
 1. Hover over a commit. A **VIEW** button appears.
 1. Click the **VIEW** button.
 
-### Compare a file to a different commit {:#compare-a-file-to-a-different-commit}
+### Compare a file to a different commit
 
 To compare a file at a different commit:
 
@@ -157,7 +157,7 @@ To change either file, hover over the commit in the Change History pane. Then,
 click either the **Left** or **Right** button to have the open the commit on the
 left or right side of the diff.
 
-### Browsing cross references {:#browsing-cross-references}
+### Browsing cross references
 
 Another way to browse source repositories is through the use of cross
 references. These references appear automatically as hyperlinks within a given
@@ -188,12 +188,12 @@ You can continue to browse cross references using the Cross Reference pane, just
 as you can in the File pane. When you do, the pane displays a breadcrumb trail,
 which you can use to navigate between different cross references.
 
-## Searching for code {:#search}
+## Searching for code
 
 You can search for specific files or code snippets using the search box located
 at the top of the screen. Searches are always against the default branch.
 
-All searches use [RE2 regular expressions](https://github.com/google/re2/wiki/Syntax){: .external}
+All searches use [RE2 regular expressions](https://github.com/google/re2/wiki/Syntax)
 by default. If you do not want to use regular expressions, enclose your search
 in double quotes ( " ).
 
@@ -270,7 +270,7 @@ f:</td>
 </tbody>
 </table>
 
-## Additional Support {:#additional-support}
+## Additional Support
 
 To report an issue, click the **Feedback** button that appears in the top
 right-hand corner of the screen and enter your feedback in the provided form.

docs/docs/android-instrumentation-test.mdx

@@ -56,7 +56,7 @@ bazel info release
 ```
 This results in output similar to the following:
 
-```none {:.devsite-disable-click-to-copy}
+```none
 release 4.1.0
 ```
 
@@ -74,7 +74,7 @@ apt-get install cpu-checker && kvm-ok
 
 If it prints the following message, you have the correct configuration:
 
-```none {:.devsite-disable-click-to-copy}
+```none
 INFO: /dev/kvm exists
 KVM acceleration can be used
 ```
@@ -95,7 +95,7 @@ which Xvfb
 ```
 The output is the following:
 
-```{:.devsite-disable-click-to-copy}
+```
 /usr/bin/Xvfb
 ```
 

docs/docs/cc-toolchain-config-reference.mdx

@@ -2,7 +2,7 @@
 title: 'C++ Toolchain Configuration'
 ---
 
-## Overview {:#overview}
+## Overview
 
 To invoke the compiler with the right options, Bazel needs some knowledge about
 the compiler internals, such as include directories and important flags.
@@ -35,7 +35,7 @@ that provides the `CcToolchainConfigInfo` and you need to point the
 You can create the `CcToolchainConfigInfo` by calling
 [`cc_common.create_cc_toolchain_config_info()`](/rules/lib/toplevel/cc_common#create_cc_toolchain_config_info).
 You can find Starlark constructors for all structs you'll need in the process in
-[`@rules_cc//cc:cc_toolchain_config_lib.bzl`](https://github.com/bazelbuild/rules_cc/blob/master/cc/cc_toolchain_config_lib.bzl){: .external}.
+[`@rules_cc//cc:cc_toolchain_config_lib.bzl`](https://github.com/bazelbuild/rules_cc/blob/master/cc/cc_toolchain_config_lib.bzl).
 
 When a C++ target enters the analysis phase, Bazel selects the appropriate
 `cc_toolchain` target based on the `BUILD` file, and obtains the
@@ -59,7 +59,7 @@ The artifacts to be shipped to the sandbox are declared in the `cc_toolchain`
 target. For example, with the `cc_toolchain.linker_files` attribute you can
 specify the linker binary and toolchain libraries to ship into the sandbox.
 
-## Toolchain selection {:#toolchain-selection}
+## Toolchain selection
 
 The toolchain selection logic operates as follows:
 
@@ -93,7 +93,7 @@ fully fledged C++ features in Bazel without modifying the
 Bazel binary. C++ rules support multiple unique actions documented in detail
 [in the Bazel source code](https://source.bazel.build/bazel/+/4f547a7ea86df80e4c76145ffdbb0c8b75ba3afa:tools/build_defs/cc/action_names.bzl).
 
-## Features {:#features}
+## Features
 
 A feature is an entity that requires command-line flags, actions,
 constraints on the execution environment, or dependency alterations. A feature
@@ -121,7 +121,7 @@ A feature is enabled in one of the following ways:
 Features can have interdependencies, depend on command line flags, `BUILD` file
 settings, and other variables.
 
-### Feature relationships {:#feature-relationships}
+### Feature relationships
 
 Dependencies are typically managed directly with Bazel, which simply enforces
 the requirements and manages conflicts intrinsic to the nature of the features
@@ -195,7 +195,7 @@ support and expansion. These are:
   </tr>
 </table>
 
-## Actions {:#actions}
+## Actions
 
 Actions provide the flexibility to modify the circumstances under
 which an action executes without assuming how the action will be run. An
@@ -216,7 +216,7 @@ that implements an action (such as `CppCompileAction`). In particular, the
 "assembler actions" and "compiler actions" in the table below are
 `CppCompileAction`, while the link actions are `CppLinkAction`.
 
-### Assembler actions {:#assembler-actions}
+### Assembler actions
 
 <table>
   <col width="300">
@@ -241,7 +241,7 @@ that implements an action (such as `CppCompileAction`). In particular, the
   </tr>
 </table>
 
-### Compiler actions {:#compiler-actions}
+### Compiler actions
 
 <table>
   <col width="300">
@@ -280,7 +280,7 @@ that implements an action (such as `CppCompileAction`). In particular, the
   </tr>
 </table>
 
-### Link actions {:#link-actions}
+### Link actions
 
 <table>
   <col width="300">
@@ -311,7 +311,7 @@ that implements an action (such as `CppCompileAction`). In particular, the
   </tr>
 </table>
 
-### AR actions {:#ar-actions}
+### AR actions
 
 AR actions assemble object files into archive libraries (`.a` files) via `ar`
 and encode some semantics into the name.
@@ -333,7 +333,7 @@ and encode some semantics into the name.
   </tr>
 </table>
 
-### LTO actions {:#lto-actions}
+### LTO actions
 
 <table>
   <col width="300">
@@ -358,7 +358,7 @@ and encode some semantics into the name.
   </tr>
 </table>
 
-## Using action_config {:#using-action-config}
+## Using action_config
 
 The `action_config` is a Starlark struct that describes a Bazel
 action by specifying the tool (binary) to invoke during the action and sets of
@@ -424,7 +424,7 @@ within the same toolchain. This prevents ambiguity in tool paths
 and enforces the intention behind `action_config` - that an action's properties
 are clearly described in a single place in the toolchain.
 
-### Using tool constructor {:#using-tool-constructor}
+### Using tool constructor
 
 An`action_config` can specify a set of tools via its `tools` parameter.
 The `tool()` constructor takes in the following parameters:
@@ -461,7 +461,7 @@ with a `with_feature` set matching the feature configuration is found
 for more information). You should end your tool lists with a default
 tool that corresponds to an empty feature configuration.
 
-### Example usage {:#example-usage}
+### Example usage
 
 Features and actions can be used together to implement Bazel actions
 with diverse cross-platform semantics. For example, debug symbol generation on
@@ -553,7 +553,7 @@ follows:
         ),
     ]
 
-### Flag groups {:#flag-groups}
+### Flag groups
 
 `CcToolchainConfigInfo` allows you to bundle flags into groups that serve a
 specific purpose. You can specify a flag within using pre-defined variables
@@ -622,7 +622,7 @@ example:
         ],
     )
 
-### Conditional expansion {:#conditional-expansion}
+### Conditional expansion
 
 Flag groups support conditional expansion based on the presence of a particular
 variable or its field using the `expand_if_available`, `expand_if_not_available`,
@@ -654,12 +654,12 @@ Note: The `--whole_archive` and `--no_whole_archive` options are added to
 the build command only when a currently iterated library has an
 `is_whole_archive` field.
 
-## CcToolchainConfigInfo reference {:#cctoolchainconfiginfo-reference}
+## CcToolchainConfigInfo reference
 
 This section provides a reference of build variables, features, and other
 information required to successfully configure C++ rules.
 
-### CcToolchainConfigInfo build variables {:#cctoolchainconfiginfo-build-variables}
+### CcToolchainConfigInfo build variables
 
 The following is a reference of `CcToolchainConfigInfo` build variables.
 
@@ -988,7 +988,7 @@ Note: The **Action** column indicates the relevant action type, if applicable.
   </tr>
 </table>
 
-### Well-known features {:#wellknown-features}
+### Well-known features
 
 The following is a reference of features and their activation
 conditions.
@@ -1092,7 +1092,7 @@ conditions.
     </tr>
 </table>
 
-#### Legacy features patching logic {:#legacy-features-patching-logic}
+#### Legacy features patching logic
 
 <p>
   Bazel applies the following changes to the toolchain's features for backwards
@@ -1142,7 +1142,7 @@ conditions.
 </p>
 
 This is a long list of features. The plan is to get rid of them once
-[Crosstool in Starlark](https://github.com/bazelbuild/bazel/issues/5380){: .external} is
+[Crosstool in Starlark](https://github.com/bazelbuild/bazel/issues/5380) is
 done. For the curious reader see the implementation in
 [CppActionConfigs](https://source.bazel.build/bazel/+/master:src/main/java/com/google/devtools/build/lib/rules/cpp/CppActionConfigs.java?q=cppactionconfigs&ss=bazel),
 and for production toolchains consider adding `no_legacy_features` to make