Consider adding forceSync=true for topic updates

[neoword]

Desired Behavior

Add forceSync=true for updating of topic metadata.

[UPDATED]

This issue is a direct result of #52, in an attempt to resolve the "dead-end" a user will inevitably run into when they get an error from #52.

Benefits

• See https://github.com/homeaway/stream-registry/blob/bacfe0a5d61fa4102bd0ff521f80d60ff90257e2/core/src/main/java/com/homeaway/streamplatform/streamregistry/db/dao/impl/KafkaManagerImpl.java#L128-L134
• Default should be forceSync=false resulting in error (current behavior)
• When users get this error, by adding forceSync=true , stream-registry can get the value from the underlying broker and "force" update itself to be in sync with the underlying broker.

[OneCricketeer]

RE: "topic: " + topic " already exists but config is different than requested!"

Should the property instead be named something along the lines of

• useExistingTopicConfig
• allowConfigIfExists
• allowConfigMismatch

[neoword]

Actually I am thinking this enhancement should sync the SR with the underlying broker metadata? @cricket007 do you agree?