[FEATURE REQUEST]Add support for MQTT in\out commands

[bthome]

Is your feature request related to a problem? Please describe.
Allow publish\subscribe via MQTT to send and receive status. For use with HomeAssistant \ NodeRed.

Describe the solution you'd like
Expose topics to support SET\GET\STATUS of all the command options and events as printer prints\moves\temp\times% complete\etc. Support of HomeAssistant MQTT Discovery (https://www.home-assistant.io/docs/mqtt/discovery/) to expose ESP3D as sensors \ automation.

Describe alternatives you've considered
Pooling is an option but would be better to allow the setup of an MQTT broker within the admin UI and define your topic "root".

Additional context

Anyway....appreciate all the work. Just started using it and like what I can do.

[github-actions]

Thank your for submiting, please be sure you followed template or your issue may be dismissed.

[luc-github]

This is a not a small task to implement this
already discussed here : #179 (comment)
and current status is here : #148

I think it can be done one day but do not close futur may be for 3.1.0 or 4.0
I left this open as reference

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[bthome]

Just as a reference, here is a link to an example of a simple implementation that could be used as a basis for integration. https://github.com/antonyx/ESP32-Serial-Bridge

[stale]

This issue has been removed from the stale queue. Please ensure activity to keep it openin the future.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This stale issue has been automatically closed. Thank you for your contributions.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.