NAMED BASE: d2032017bb, Besu tag 26.4.0

The files in this directory are applied ON TOP of a Besu tree at EXACTLY that commit. Applied to
anything else they overwrite, and silently delete, whatever upstream added in between. Measured
against a newer base, 26.7.1: 97 lines would be lost, among them the registration of the /liveness
and /readiness probes in BesuCommand.java, and nothing would fail.

IF YOU MOVE THE BASE, do not take whole files from here. Re-apply the same changes as a patch
against your own base: a patch fails loudly when upstream has moved, a whole file does not.

The finding, in one line: shipping whole files is a silent overwrite, not a merge. That is why the
base commit is named here rather than left implicit, and it is why the same code is delivered to the
node repository as a patch and not as a tree.

Clean upstream tree at that commit: 4,118 .java files. If your count differs, you are not on the
base this overlay was measured against.