[Fix][Kafka-Sink] fix kafka sink factory option rule

[liunaijie]

Purpose of this pull request

the current kafka sink factory option rule has some wrong usage.

from the current code, topic only required when format is in (json, cancal_json, text, ....), but it should be required whether the format is.
and we don't need limit the format value, because it's an enum, if pass an wrong value, it will get error when parse value. and all of the format is supported

Does this PR introduce any user-facing change?

How was this patch tested?

Check list

• If any new Jar binary package adding in your PR, please add License Notice according
  New License Guide
• If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs
• If you are contributing the connector code, please check that the following files are updated:
  1. Update change log that in connector document. For more details you can refer to connector-v2
  2. Update plugin-mapping.properties and add new connector information in it
  3. Update the pom file of seatunnel-dist
• Update the release-note.

[EricJoy2048]

Why remove this? conditional option can help SeaTunnel Web auto create connector form.

[liunaijie]

because i find this rule is only check topic parameter exist when format is in (json, cancal_json, text, ....), but it required whether the format is. so i remove it.
if the web need use this, i will add this conditional option back.

[liunaijie]

Why remove this? conditional option can help SeaTunnel Web auto create connector form.

@Hisoka-X i remove it before, but eric said it will be used in web. so i put it back and move the topic option check in conditional, just put it to required

[hailin0]

why requiredOptions is null?

[liunaijie]

move topic to required check. if in the conditional, it only required when format type is in the list. if other format is add and using this format, it doesn't required topic parameter, then in the next steps will get exception

[Hisoka-X]

So as you said, I think we should remove this conditional.

[EricJoy2048]

Sorry, I made a mistake. I have reviewed the code for seatunnel-web again and can delete the option.

[liunaijie]

removed.
I have some question about the optional rule. we know if in required, then we must pass the parameter. if in optional, we can pass or not pass this parameter.
But we still can pass some unknown parameter to the config, like this

sink {
  kafka {
     topic = ""
     bootstrap.servers = ""
     k1 = v1
     k2 = v2
  }
}

i pass 2 parameter k1 and k2. it is not in option list and won't be use in feature.
So what's the option rule value? it can't control anything

[Hisoka-X]

It can verify the legality of the value corresponding to a meaningful key, thereby ensuring the normal operation of the job, and that unexpected values can be fed back to the user as early as possible. But for useless keys, not telling users to delete them is based on two principles: 1. These keys will not affect the normal operation of the job. 2. If we delete a key, the key may still exist in the user's own config. We hope that the user can run job normally without changing the config.

[Hisoka-X]

LGTM