[fix][broker] Fix the replicator unnecessary get schema request for BYTES schema

[codelipenghui]

Motivation

We can see many logs like the following (not master since #16345 has changed to level to debug)

And it is easy to reproduce. You can just create a geo-replicated cluster
and produce the bytes messages.

It should be related to this change #17049 (haven't released) which fixed the replicated schema issue.
But we shouldn't get the schema from the broker for the BYTES schema, the client side will not cache the BYTES schema.
So, the replicator tries to get the schema again and again.

pulsar/pulsar-client/src/main/java/org/apache/pulsar/client/impl/ProducerImpl.java

Lines 756 to 763 in eab2bb5

	log.info("[{}] [{}] GetOrCreateSchema succeed", topic, producerName);
	// In broker, if schema version is an empty byte array, it means the topic doesn't have schema. In this
	// case, we should not cache the schema version so that the schema version of the message metadata will
	// be null, instead of an empty array.
	if (v.length != 0) {
	schemaCache.putIfAbsent(msg.getSchemaHash(), v);
	msg.getMessageBuilder().setSchemaVersion(v);
	}

Modifications

The fix is the same as the normal messages with AUTO_PRODUCE producer do

pulsar/pulsar-client/src/main/java/org/apache/pulsar/client/impl/ProducerImpl.java

Lines 709 to 713 in eab2bb5

	if (msg.getSchemaInternal() == schema) {
	schemaVersion.ifPresent(v -> msgMetadataBuilder.setSchemaVersion(v));
	msg.setSchemaState(MessageImpl.SchemaState.Ready);
	return true;
	}

If the users will not change the message schema(send with bytes), the message schema is also AUTO_PRODUCE,
so the producer will not try to fetch schema from the broker.

Verifying this change

New test added.

Does this pull request potentially affect one of the following parts:

If yes was chosen, please highlight the changes

• Dependencies (does it add or upgrade a dependency): (no)
• The public API: (no)
• The schema: (no)
• The default values of configurations: (no)
• The wire protocol: (no)
• The rest endpoints: (no)
• The admin cli options: (no)
• Anything that affects deployment: (no)

Documentation

Check the box below or label this PR directly.

Need to update docs?

• doc-required
  (Your PR needs to update docs and you will update later)

• doc-not-needed
  (Please explain why)

• doc
  (Your PR contains doc changes)

• doc-complete
  (Docs have been already added)