[Test] Remove Auth0 service dependency from all unit tests

[lhotari]

Description

Auth0 service dependency in TokenOauth2AuthenticatedProducerConsumerTest was removed in #20465.

It turns out that there is an Auth0 service dependency also in these 2 locations:

pulsar/pulsar-proxy/src/test/java/org/apache/pulsar/proxy/server/ProxyTlsTestWithAuth.java

Lines 67 to 70 in d565c95

	proxyConfig.setBrokerClientAuthenticationParameters("{\"grant_type\":\"client_credentials\"," +
	" \"issuerUrl\":\"https://dev-kt-aa9ne.us.auth0.com\"," +
	" \"audience\": \"https://dev-kt-aa9ne.us.auth0.com/api/v2/\"," +
	" \"privateKey\":\"file://" + tempFile.getAbsolutePath() + "\"}");

pulsar/pulsar-testclient/src/test/java/org/apache/pulsar/testclient/Oauth2PerformanceTransactionTest.java

Lines 87 to 89 in 82237d3

	params.put("issuerUrl", new URL("https://dev-kt-aa9ne.us.auth0.com"));
	params.put("privateKey", path.toUri().toURL());
	params.put("audience", "https://dev-kt-aa9ne.us.auth0.com/api/v2/");

These should also be covered.

An additional detail is that it would be better to change the OAuth2 audience claim https://dev-kt-aa9ne.us.auth0.com/api/v2/ in TokenOauth2AuthenticatedProducerConsumerTest during this change since that could cause confusion for future maintainers.

Implementation hints

It's possible to share test classes via pulsar-broker test-jar dependency:

        <dependency>
          <groupId>${project.groupId}</groupId>
          <artifactId>pulsar-broker</artifactId>
          <version>${project.version}</version>
          <scope>test</scope>
          <type>test-jar</type>
        </dependency>

This is already specified in pulsar-proxy/pom.xml and pulsar-testclient/pom.xml

It would be possible to extract some test classes from TokenOauth2AuthenticatedProducerConsumerTest for Wiremocking OAuth and put the classes under some package in pulsar-broker/src/test/java/org/apache/pulsar . This would be a way to reduce code duplication across tests where similar logic is needed.

[michaeljmarshall]

Great points @lhotari. I can follow up on this tomorrow.