Consider tweaking client options a bit

[DirectXMan12]

I believe (been mulling this over a bit) that we can make it so that client options don't require different functions when the same option occurs, but the trade-offs are a bit strange in terms of compatibility. TL;DR is that we define an interface to accept as options instead of functions, and then structs can implement multiple different interfaces.

The downside is that the options functions now return a concrete type, which means that type is now part of the public interface, despite being a bit of an implementation detail. The alternative is returning an umbrella-interface, but that means that every time we add an element, it's a breaking change (since the function signature changes).

[DirectXMan12]

/kind feature
/priority backlog

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[DirectXMan12]

closing, fixed in #536