feat: add support for dockerd Builder-Version header

[rroesch1]

• in docker 23 dockerd introduced the 'Builder-Version' header to expose the recommended version of the builder backend
• it is up to the client to follow this recommendation
• dockerd uses the deprecated 'classic builder' if clients do not set the 'version' build option explicitly
• d-m-p should always set the 'version' option as recommended by the dockerd

Refs: #1711

[sonarqubecloud]

Quality Gate failed

Failed conditions
40.9% Coverage on New Code (required ≥ 80%)

See analysis details on SonarCloud

[rohanKanojia]

@rroesch1 : Some integration tests seem to be failing. Could you please take a look at these failures?

[rroesch1]

@rroesch1 : Some integration tests seem to be failing. Could you please take a look at these failures?

Well, i got that but it took me while to realize what's going wrong here:

• I am sorry to say it isn't that easy to get buildkit support …
• enabling buildkit actually works, but builds may fail in some cases
• The reason for this is, that buildkit expects to have some sort of "callback api" to the client. To provide this callback, the client has to initiate a gRPC session (see: Initialize interactive session API) + the client has to implement several gRPC services.
• I couldn't find any documentation about these services, but the code for these seem to here here
• Creating (and maintaining) a Java implementation for these gRPC services is probably a monstrous task. I am afraid to say that it's probably easier to stop using the Docker Engine API at all and use the CLI (docker build(x)) instead. At least for now i have no clue how to deal with that.