Do we need BuilderPreferences?

In Gloas, we introduced `BuilderPreferences` which is a per builder preference expressed by validators. The builder preference structure looks like the below:
```
class BuilderPreferences(Container):
max_trusted_bid: Gwei
```

The max_trusted_bid is the maximum amount of the bid which will be accepted in a trusted payment.

The max_trusted_bid is very useful in situations where the proposer doesn't want to trust a builder to pay it via the execution layer and enforces it to pay only via the trustless payments mechanism.

We could also make the argument that the proposer could just disconnect from the builder in such cases. It is also not trivial for an operator know what to configure the max_trusted_bid to at any given time and they would just ideally just configure it to UINT64_MAX.

If we remove the `BuilderPreferences`, it would make the Builder-API stateless and make the spec very simple. Can we remove it?

Start by reviewing the BuilderPreferences definition and the surrounding Builder-API behavior described in the issue. Determine whether removing the preference preserves the trusted-payment requirements and makes the API stateless; done means reaching and documenting a maintainer decision.

Written by the indexing model from the issue text.