read_replica: reject setting `remote.read/write` on read replica topics

[LenaAn]

Who is this for and what problem do they have today?

Customer who created read replica topic may accidentaly set redpanda.remote.read/write params via alter config. If topic is a read replica, them archival/shadow indexing doesn't apply to this topic.

What are the success criteria?

When user tries to set remote.read/write to read replica topic, user should get an error with a comprehensive error message.

Why is solving this problem impactful?

Additional notes