Why are all functions prefaced with esp_mqtt_client_, except for two which are simply esp_mqtt_ (IDFGH-16114)

[hachi]

Checklist

• Checked the issue tracker for similar issues to ensure this is not a duplicate.
• Provided a clear description of your suggestion.
• Included any relevant context or examples.

Issue or Suggestion Description

In particular I'm referring to

esp_mqtt_set_config and esp_mqtt_dispatch_custom_event

They still take a client as the first argument, so the inconsistency is a little weird.

I noticed this when I tried to call esp_mqtt_client_set_config which I was nearly certain existed... and failed to compile.

[euripedesrocha]

@hachi Thanks for reporting, there might be a historical reason on code style changes and we being blocked to introduce breaking changes between versions (or that we missed it once feature was introduced).

We'll have a major update on the mqtt client later this year, and I'll keep this open to fix when the time comes. We are also open to accept PRs from features that you think should be introduced and fixes.

Need to highlight that I very much appreciate your contribution pointing those issues that we missed. Thank you.