Register MODULE.bazel.lock as JSON and generated

[dtolnay]

Description

This PR makes Linguist recognize files named "MODULE.bazel.lock" as generated and also as JSON syntax.

Real-world examples:

• https://github.com/bazelbuild/bazel/blob/master/MODULE.bazel.lock
• https://github.com/carbon-language/carbon-lang/blob/trunk/MODULE.bazel.lock
• https://github.com/dtolnay/cxx/blob/master/MODULE.bazel.lock

Bazel (https://bazel.build) outputs these lockfile since version 6.2.0. Announcement: https://blog.bazel.build/2023/07/24/whats-new-with-bzlmod.html. More details about Bazel lockfiles: https://bazel.build/external/lockfile.

Checklist:

• I am fixing a misclassified language

  • I have included a new sample for the misclassified language:
    • Sample source(s):
      • obtained by running mkdir bzlmod && cd bzlmod && touch MODULE.bazel && touch BUILD.bazel && bazel build ...
    • Sample license(s):
      • generated by Bazel, so Bazel's license: Apache License 2.0
  • I have included a change to the heuristics to distinguish my language from others using the same extension.

• I am adding new or changing current functionality

  • I have added or updated the tests for the new or changed functionality.

[lildude]

The sample file is waaay too big so is suppressed by the diff by default as would be the case when this PR is merged. Is it possible to generate a smaller file?

[dtolnay]

The original MODULE.bazel.lock (1037 lines) is what Bazel generates for an empty repo, so I don't know a way to generate a smaller one. It tracks the transitive dependencies of the @bazel_tools repo, which is embedded in Bazel and included as a mandatory dependency of every project. Among other things, it exposes foundational concepts like the constraint definitions that determine Bazel's understanding of things like "os:linux" and "cpu:x86_64".

For now I have edited it manually to delete some verbose fields.

[lildude]

LGTM. Thanks.

Note: this PR will not be merged until close to when the next release is made. See here for more details.