ci: prepare for new mdformat

.github/ISSUE_TEMPLATE/feature_request.md

@@ -11,8 +11,7 @@ example, is this related to bigtable (i.e., something in
 `google/cloud/bigtable`), or GCS (i.e., something in `google/cloud/storage`)?
 
 **Is your feature request related to a problem? Please describe.** A clear and
-concise description of what the problem is. Ex. I'm always frustrated when
-\[...\]
+concise description of what the problem is. Ex. I'm always frustrated when [...]
 
 **Describe the solution you'd like** A clear and concise description of what you
 want to happen.

ci/cloudbuild/dockerfiles/checkers.Dockerfile

@@ -46,8 +46,9 @@ RUN curl -L -o /usr/local/bin/shfmt https://github.com/mvdan/sh/releases/downloa
 RUN pip3 install --upgrade pip
 RUN pip3 install cmake_format==0.6.13
 RUN pip3 install black==22.3.0
-RUN pip3 install mdformat-gfm==0.3.5 \
-                 mdformat-frontmatter==0.4.1 \
+RUN pip3 install mdformat==0.7.19 \
+                 mdformat-gfm==0.3.7 \
+                 mdformat-frontmatter==2.0.8 \
                  mdformat-footnote==0.1.1
 
 RUN curl -o /usr/bin/bazelisk -sSL "https://github.com/bazelbuild/bazelisk/releases/download/v1.24.0/bazelisk-linux-${ARCH}" && \

doc/ctype-cord-workarounds.md

@@ -77,7 +77,7 @@ present, this is the correct default with **any** Protobuf version.
 
 Once the `[ctype = CORD]` annotation is included in the proto files then the
 correct default depends on the Protobuf version. If `google-cloud-cpp` is using
-Protobuf \< v23 and the annotation is included in the proto files, then
+Protobuf < v23 and the annotation is included in the proto files, then
 `google-cloud-cpp` will enable the workarounds by default.
 
 It is very likely that the default value for this option is incorrect during the

google/cloud/bigtable/README.md

@@ -71,7 +71,7 @@ int main(int argc, char* argv[]) try {
 - Official documentation about the [Cloud Bigtable][cloud-bigtable-docs] service
 - [Reference doxygen documentation][doxygen-link] for each release of this
   client library
-- Detailed header comments in our \[public `.h`\]\[source-link\] files
+- Detailed header comments in our \[public `.h`\][source-link] files
 
 [cloud-bigtable-docs]: https://cloud.google.com/bigtable/docs/
 [doxygen-link]: https://cloud.google.com/cpp/docs/reference/bigtable/latest/

google/cloud/opentelemetry/quickstart/README.md

@@ -84,7 +84,7 @@ enables OpenTelemetry tracing instrumentation in `google-cloud-cpp`.
 build --@google_cloud_cpp//:enable_opentelemetry
 ```
 
-If you are using an OpenTelemetry version \< v1.16.0, you must also supply the
+If you are using an OpenTelemetry version < v1.16.0, you must also supply the
 following flag for compatibility with Abseil. Without this flag, the above
 `bazel build ...` command will fail.
 

google/cloud/publicca/README.md

@@ -1,7 +1,7 @@
 # Public Certificate Authority API C++ Client Library
 
-This directory contains an idiomatic C++ client library for the \[Public
-Certificate Authority API\]\[cloud-service-docs\].
+This directory contains an idiomatic C++ client library for the
+[Public Certificate Authority API][cloud-service-docs].
 
 The Public Certificate Authority API may be used to create and manage ACME
 external account binding keys associated with Google Trust Services' publicly

release/README.md

@@ -331,7 +331,7 @@ PR, similar to [PR#138]. If you want, subscribe to notifications in the
 [conda feedstock repository] or just look at the PRs in that repository over the
 next 24 hours.
 
-## 8. \[optional\] Push the release to Conan
+## 8. [optional] Push the release to Conan
 
 The documentation has moved to the
 [How-To Guide: Update Conan Package](/release/howto-update-conan-package.md).