fix: reinstate the old KsqlRestClient.create overload

[swist]

Description

Commit a33b1e6
has changed the create method signature without
deprecating the old one first, causing the drift benchmarks
to fail with:

java.lang.NoSuchMethodError: io.confluent.ksql.rest.client.KsqlRestClient.create(
	java/lang/String;
	java/util/Map;
	java/util/Map;
	java/util/Optional;
)
io/confluent/ksql/rest/client/KsqlRestClient;

We're just adding back the missing signagure

Testing done

No test changes, just added a basic sanity check that we don't remove the signature later down the line

Reviewer checklist

• Ensure docs are updated if necessary. (eg. if a user visible feature is being added or changed).
• Ensure relevant issues are linked (description should include text like "Fixes #")

[cadonna]

LGTM!

Thanks @swist !

[vcrfxia]

KsqlRestClient is not a public API. Why can't we just update the benchmarks repo to pass the additional Optional.empty() param? I can make the change if you'd like.

[swist]

@vcrfxia I've looked at updating the benchmarks repo - the call doesn't live in the benchmarks repo itself, rather in the drift framework one, we would have to do some additional maven-fu to make sure that picks the correct version - drift uses confluent.version ref while drift-benchmark uses a custom range to resolve the nano versions. The most reliable way is to bring back the missing signature like this PR does