Expose `scrub.invalid.names` config to scrub invalid schema names

[mukkachaitanya]

Problem

https://github.com/confluentinc/schema-registry/pull/1873 introduced the option to scrub invalid schema names, but the storage connectors can't take advantage of it as it's not an exposed config.

Solution

Expose the option to be configured. A lucrative alternative here would be instead to have a passthrough, say formatter.avro.* which let through all of AvroDataConfig options instead of exposing them one by one.

Does this solution apply anywhere else?

• [ ] yes
• [X] no

If yes, where?

Test Strategy

Testing done:

• [X] Unit tests
• [ ] Integration tests
• [ ] System tests
• [ ] Manual tests

Release Plan