[monitor-query][test] logsQueryClient unit test should not rely on ServiceClient internals

[jeremymeng]

Currently the test passes a custom endpoint via option then verify that private/protected properties of the generated client are set.

azure-sdk-for-js/sdk/monitor/monitor-query/test/internal/unit/logsQueryClient.unittest.spec.ts

Lines 35 to 36 in 07a98c6

	assert.equal(client["_logAnalytics"].$host, "https://customEndpoint1");
	assert.equal(client["_logAnalytics"]["_baseUri"], "https://customEndpoint1");

We can improve the test by testing that the option is passed to ServiceClient via a mock, instead of verifying the internals of ServiceClient.

[sarangan12]

Checked this code. There are 2 levels of validation that is happening in this test:

1. Checking the Endpoints
2. Checking the error message.

Here, if I try to check the endpoints using the mock client, then this would need the ability to modify the pipeline policy which is not currently exposed. So, doing this would be more related to a feature work for which there is no real need. So, closing this issue and keeping the tests as such. No further action required.