MLE-23230 Applying RetryInterceptor in test plumbing

[rjrudin]

This avoids hardcoding it in the actual client and let's us still see the results for the tests.

Also fixed a warning from Polaris about the interceptor.

[Copilot]

Pull Request Overview

This PR moves the RetryInterceptor configuration from being hardcoded in production code to being applied through test configuration. The key purpose is to enable retry functionality during tests while removing it from the production client code.

Key changes:

• Removes hardcoded RetryInterceptor from production OkHttpUtil class
• Adds RetryInterceptor configuration via DatabaseClientFactory configurators in test classes
• Makes RetryInterceptor class and constructor public to enable external usage

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File	Description
Common.java	Adds static block to configure RetryInterceptor for tests via DatabaseClientFactory
RetryInterceptor.java	Changes class and constructor visibility to public; improves unreachable code handling
OkHttpUtil.java	Removes hardcoded RetryInterceptor from production client builder
ConnectedRESTQA.java	Adds static block to configure RetryInterceptor for functional tests

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

[nitpick] The comment and exception message are redundant. Consider simplifying to just throw new IllegalStateException("Unexpected end of retry loop"); since the comment already explains this should never be reached.

Suggested change

	throw new IllegalStateException("Retry loop completed without returning or throwing - this should not happen");
	throw new IllegalStateException("Unexpected end of retry loop");