Add builder boost factor part1

[tbenr]

• Adds requestedBuilderBoostFactor eventually coming from BlockV3
• The requestedBuilderBoostFactor will always override the eventual comparison factor configured on BN side.
• Uniforms our internal builderComparisonFactor representation to the new param (from Optional<Integer> to Uint64) so the handling is simplified

In our CLI we could support PREFER_BUILDER as an alias to BUILDER_ALWAYS and start advertising the new maintaining backward compatibility (separate PR)

related to #7851

Documentation

• I thought about documentation and added the doc-change-required label to this PR if updates are required.

Changelog

• I thought about adding a changelog entry, and added one if I deemed necessary.

[zilm13]

LGTM, but it would be great to see some more tests for it. They could be probably done in separate PR if not forgotten
Tests could include:

1. builderBoost input is delivered to ExecutionBuilderModule.builderGetHeader() from any source (we have very branchy createBlock flow, all looks impossible, but at least any)
2. more like builderGetHeaderGetPayload_shouldGivePriorityToRequestedBuilderBoostFactor, maybe unit tests for methods from ExecutionBuilderModule, even in API description it's highlighted to be careful with overflow and there could be bunch of others cases (I see by eyes that it shouldn't overflow, but who knows!)
3. Maybe considering verbosity and size of current integration tests there is a sense to do just a unit tests for isLocalPayloadValueWinning and maybe logLocalPayloadWin

[tbenr]

My plan is to move value comparison tests on a separate PR

[zilm13]

LGTM