Should KubernetesMockServer.reset() also reset DefaultMockServer.lastRequest*

[gsmet]

Is your enhancement related to a problem? Please describe

In

kubernetes-client/junit/kubernetes-server-mock/src/main/java/io/fabric8/kubernetes/client/server/mock/KubernetesMockServer.java

Lines 230 to 237 in 5fd904c

	public void reset() {
	clearExpectations();
	onStart();
	unsupportedPatterns.clear();
	if (this.dispatcher instanceof Resetable) {
	((Resetable) this.dispatcher).reset();
	}
	}

, we don't reset the fields that are in DefaultMockServer and especially these three:

kubernetes-client/junit/mockwebserver/src/main/java/io/fabric8/mockwebserver/DefaultMockServer.java

Lines 40 to 42 in 5fd904c

	private final Map<ServerRequest, Queue<ServerResponse>> responses;
	private final AtomicInteger lastRequestCount;
	private final AtomicReference<RecordedRequest> lastRequest;

(but there might be others that make sense) .

It can be problematic when you actually try to check that no request have been sent with getLastRequest() after a reset() and some operations and you end up with the request sent pre-reset().

Describe the solution you'd like

Ideally, I would like DefaultMockServer to be reset when KubernetesMockServer is reset.

Describe alternatives you've considered

No response

Additional context

It looks like it comes out of the blue but I noticed it while doing some enhancements on sbomer and it got in the way.

[manusa]

Good catch, this does seem like a bug.