request a rebuild to pick up Pygments 2.21.0

[Trevor Woerner <twoerner@gmail.com>]

Hi,

Could someone build buildtools-docs against current master and publish
the result?

scripts/run-docs-build line 29 pins the docs toolchain to the
yocto-6.0_M2 tarball, which ships Pygments 2.19.2. The newest
published milestone, yocto-6.1_M2, has 2.20.0. OE-Core master carries
python3-pygments_2.21.0.bb.

2.21.0 is the release that added a BitBake lexer, so it is the first
version in which

	.. code-block:: bitbake

does anything at all. I have a conversion of the BitBake snippets
in yocto-docs and the BitBake user manual ready to send, but on the
current toolchain every block would publish unhighlighted - and since
run-docs-build drops the Makefile's -W, silently.

I've tested the change. run-docs-build feeds every BitBake docs branch
through $builddir/buildtools unconditionally, and yocto-docs from
scarthgap forward, so I built all of them twice - once with 2.19.2,
once with 2.21.0 - applying the same docs-build-patches and master-file
checkouts the script does:

	bitbake     1.46 through 2.18, and master          14/14 identical
	yocto-docs  scarthgap styhead walnascar whinlatter   4/4 identical

36 builds, same exit status, same warning count - zero warnings
throughout.

Best regards,
	Trevor