[build] Use clang-format from bzlmod

[jwnimmer-tri]

Towards #20731 and #21714 and #14967 and #4843.

For now, the clang-format remains pinned to 15 (no change). In a future PR, I'll aim to upgrade that to the latest and greatest.

---

This change is 

[jwnimmer-tri]

+@xuchenhan-tri for feature review of the code parts, please (not necessarily the doc/** parts, though you are welcome to skim that too). After we think the code is okay, I'll seek out individual feature reviewers for each of the IDEs we need to manually re-test.

[xuchenhan-tri]

on everything outside of doc/.

Reviewed 15 of 15 files at r1, all commit messages.
Reviewable status: 3 unresolved discussions, needs at least two assigned reviewers, labeled "do not merge" (waiting on @jwnimmer-tri)

---

doc/_pages/code_style_tools.md line 57 at r1 (raw file):

For development on Ubuntu: format a file that has been staged in git

git clang-format --binary=/path/to/drake/bazel-bin/tools/lint/clang-format -- [file name]

BTW, to be more clear, remind people to build it first?

---

MODULE.bazel line 78 at r1 (raw file):

# Add additional modules we use as tools (not runtime dependencies).

bazel_dep(name = "toolchains_llvm", version = "1.2.0")

BTW, is there a particular reason that we don't use the latest release 1.3.0?

---

tools/lint/clang_format_lint.py line 35 at r1 (raw file):

    print("ERROR: {} needs clang-format".format(filename))
    print("note: fix via {} -style=file -i {}".format(
        "bazel-bin/tools/lint/clang-format", filename))

BTW, remind people to build it when necessary?

[jwnimmer-tri]

Reviewable status: 3 unresolved discussions, needs at least two assigned reviewers, labeled "do not merge"

---

MODULE.bazel line 78 at r1 (raw file):

Previously, xuchenhan-tri wrote…

BTW, is there a particular reason that we don't use the latest release 1.3.0?

Heh. Because it was released 6 hours ago =P.

I'll check to see if it still works for us.

[xuchenhan-tri]

Reviewable status: 3 unresolved discussions, needs at least two assigned reviewers, labeled "do not merge" (waiting on @jwnimmer-tri)

---

MODULE.bazel line 78 at r1 (raw file):

Previously, jwnimmer-tri (Jeremy Nimmer) wrote…

Heh. Because it was released 6 hours ago =P.

I'll check to see if it still works for us.

Aha, glad I checked!

[xuchenhan-tri]

Reviewed 3 of 3 files at r2, all commit messages.
Reviewable status: needs at least two assigned reviewers, labeled "do not merge" (waiting on @jwnimmer-tri)

[SeanCurtis-TRI]

+@SeanCurtis-TRI evaluating vs code instructions.

[SeanCurtis-TRI]

The slight modification to the vscode docs check out.

Reviewed 1 of 15 files at r1.
Reviewable status: 1 unresolved discussion, labeled "do not merge" (waiting on @jwnimmer-tri)

---

doc/_pages/vscode.md line 32 at r2 (raw file):

In the VS Code Options configuration, check that the option for
``C_Cpp: Clang_format_path`` is set to Drake's preferred value
``/path/to/drake/bazel-bin/tools/lint/clang-format``.

BTW You might consider specifically calling out setting it in the Workspace settings instead of the user settings.

[jwnimmer-tri]

Reviewable status: 1 unresolved discussion, labeled "do not merge" (waiting on @jwnimmer-tri)

---

doc/_pages/vscode.md line 32 at r2 (raw file):

Previously, SeanCurtis-TRI (Sean Curtis) wrote…

BTW You might consider specifically calling out setting it in the Workspace settings instead of the user settings.

Sorry, I don't know what that means.

I've opened the branch to pushes, maybe you could push the new text?

[SeanCurtis-TRI]

Reviewable status: labeled "do not merge" (waiting on @jwnimmer-tri)

---

doc/_pages/vscode.md line 32 at r2 (raw file):

Previously, jwnimmer-tri (Jeremy Nimmer) wrote…

Sorry, I don't know what that means.

I've opened the branch to pushes, maybe you could push the new text?

Ah, vscode settings come in two kinds. One is user-level and one is workspace-level. Because this change is appropriate to Drake, it would make sense to set this value in the workspace settings for Drake. Although, it's probably harmless to set it in user settings as long as you're content to apply clang-format-15 to all projects.

It's probably not of great significance.

[sherm1]

the revised External Tool instructions for CLion work well

Reviewed 9 of 15 files at r1, 2 of 3 files at r2, 4 of 4 files at r3, all commit messages.
Reviewable status: labeled "do not merge" (waiting on @jwnimmer-tri)