KAFKA-17192 Fix MirrorMaker2 worker config does not pass config.provi…

[k0b3rIT]

…ders value to connectors

A new method got introduced beside the existingentriesWithPrefix with an extended parameter list (allowMatchingLength) that allows the user to configure its behavior when the property key is exactly the same as the prefix.

Testing:
Worker config test got extended to assert on a property (config.providers) that matches with the prefix

Committer Checklist (excluded from commit message)

• Verify design and implementation
• Verify test coverage and CI build status
• Verify documentation (including upgrade notes)

[OmniaGM]

@k0b3rIT duplicate PR with #16677

[k0b3rIT]

@k0b3rIT duplicate PR with #16677

Actually this is for the trunk, and the other one is for the 3.7.
I am not sure how the backporting process works. I ran into this on 3.7, but noticed that its present on the trunk too. Thats why I opened PR for both

[OmniaGM]

Usually the PR get merged to trunk first then cherry-pick the pr commit from trunk into the release branch

[C0urante]

Can we add a Javadoc for this? It can be largely identical to the one above, just needs to include an additional description for the allowMatchingLength parameter.

[k0b3rIT]

sure, I have added it

[C0urante]

Thanks @k0b3rIT! Looks good for the most part, just one small comment request. Can you also add a description for the changes to your PR (where the "More detailed description of your change" template currently is)?

[k0b3rIT]

Thanks @k0b3rIT! Looks good for the most part, just one small comment request. Can you also add a description for the changes to your PR (where the "More detailed description of your change" template currently is)?

All done, Thanks a lot!

[C0urante]

LGTM, thanks!

[C0urante]

@cmccabe I'd like to backport this low-risk change to 3.9. Is that alright with you?

[C0urante]

@k0b3rIT I can backport this to 3.7 and 3.8 once it's also backported to 3.9. We've just cut a new branch for the upcoming 3.9.0 release so I've asked the release manager if it's okay to backport this to 3.9 right now. If we can't backport to 3.9 right now, I'll be sure to backport it to 3.9, 3.8, and 3.7 once 3.9.0 is released.

[cmccabe]

I don't see why we can't backport to 3.9

[C0urante]

Thanks Colin! Backported to 3.9.

[C0urante]

And 3.8.

[C0urante]

Aaaaaand 3.7.