Adjust the judgment logic of topic schema operation permissions

[yuruguo]

Is your enhancement request related to a problem? Please describe.
The role(not super-user) that has the lookup topic permission should also have the operation permission of the topic schema, for example, the role could get topic schema through ./bin/pulsar-admin schemas get tenant1/ns1/tp1.
But I found that we first judge whether the role has access to the tenant of this topic, as below:

pulsar/pulsar-broker/src/main/java/org/apache/pulsar/broker/admin/v2/SchemasResource.java

Lines 82 to 91 in a455d06

	public void getSchema(
	@PathParam("tenant") String tenant,
	@PathParam("namespace") String namespace,
	@PathParam("topic") String topic,
	@QueryParam("authoritative") @DefaultValue("false") boolean authoritative,
	@Suspended final AsyncResponse response
	) {
	validateTopicName(tenant, namespace, topic);
	getSchema(authoritative, response);
	}

pulsar/pulsar-broker/src/main/java/org/apache/pulsar/broker/admin/impl/SchemasResourceBase.java

Lines 87 to 94 in a455d06

	public void getSchema(boolean authoritative, AsyncResponse response) {
	validateDestinationAndAdminOperation(authoritative);
	String schemaId = getSchemaId();
	pulsar().getSchemaRegistryService().getSchema(schemaId).handle((schema, error) -> {
	handleGetSchemaResponse(response, schema, error);
	return null;
	});
	}

pulsar/pulsar-broker/src/main/java/org/apache/pulsar/broker/admin/impl/SchemasResourceBase.java

Lines 309 to 312 in a455d06

	private void validateDestinationAndAdminOperation(boolean authoritative) {
	try {
	validateAdminAccessForTenant(topicName.getTenant());
	validateTopicOwnership(topicName, authoritative);

L311's effect is to check the http client role has admin access to the specified tenant.
Since the role only has the authority to lookup this topic, so it cannot be passed.
I have doubts about the rationality of this judgment( call L311), and we should converge the scope of this judgment.

Describe the solution you'd like
Remove this judgment, and replace it with a judgment whether the role has the lookup permission for this topic, as below:

    private void validateDestinationAndAdminOperation(boolean authoritative) {
        try {
            // validateAdminAccessForTenant(topicName.getTenant());
            validateTopicOwnership(topicName, authoritative);
            validateTopicOperation(topicName, TopicOperation.LOOKUP);

[github-actions]

The issue had no activity for 30 days, mark with Stale label.

[tisonkun]

@yuruguo Perhaps we should reopen this issue before #16018 merged?

[yuruguo]

@yuruguo Perhaps we should reopen this issue before #16018 merged?

Yep, done.