Search before asking

• I had searched in the issues and found no similar issues.

What happened

When the project began loading the plugin, we encountered multiple jars during the search due to custom development（eg ⬇️：plugin-mapping.properties）. I propose using a similarity algorithm to match the most appropriate jar. Please review the details, and I will submit the corresponding pr.

SeaTunnel Version

2.3.3 When I raised this issue, I found that 2.3.5 had already avoided this by throwing IllegalArgumentException

SeaTunnel Config

plugin-mapping.properties
---
seatunnel.source.HttpBase = connector-http
seatunnel.sink.HttpBase = connector-http
seatunnel.source.HttpJira = connector-http-jira
seatunnel.sink.HttpJira = connector-http-jira
seatunnel.source.Kafka = connector-kafka
seatunnel.sink.Kafka = connector-kafka
seatunnel.source.Kafka-Alcs = connector-kafka-alcs
seatunnel.sink.Kafka-Alcs = connector-kafka-alcs
seatunnel.source.Kafka-Blcs = connector-kafka-blcs
seatunnel.sink.Kafka-Blcs = connector-kafka-blcs
---

Running Command

-

Error Exception

-

Zeta or Flink or Spark Version

No response

Java or Scala Version

No response

Screenshots

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct