0217 improve frame too large logging context

[zmstone]

Release version: v/e5.6.0

Summary

• Log parsed bytes and bytes limit for frame_too_large error
• Refactored connect packet parse failures to include more details

example trace:

2024-02-18T19:40:28.241495+01:00 [MQTT] test@127.0.0.1:47552 msg: mqtt_packet_received, packet: {frame_error,#{limit => 100,cause => frame_too_large,received => 143}}
2024-02-18T19:40:28.241765+01:00 [SOCKET] test@127.0.0.1:47552 msg: socket_force_closed, reason: frame_too_large
2024-02-18T19:40:28.242150+01:00 [SOCKET] test@127.0.0.1:47552 msg: emqx_connection_terminated, reason: {shutdown,frame_too_large}

PR Checklist

Please convert it to a draft if any of the following conditions are not met. Reviewers may skip over until all the items are checked:

• Added tests for the changes
• Added property-based tests for code which performs user input validation
• Changed lines covered in coverage report
• Change log has been added to changes/(ce|ee)/(feat|perf|fix|breaking)-<PR-id>.en.md files
• For internal contributor: there is a jira ticket to track this change
• Created PR to emqx-docs if documentation update is required, or link to a follow-up jira ticket
• Schema changes are backward compatible

Checklist for CI (.github/workflows) changes

• If changed package build workflow, pass this action (manual trigger)
• Change log has been added to changes/ dir for user-facing artifacts update

[ieQu1]

Suggested change

	Enhanced `frame_too_large` and malformed CONNECT packet parse failures to include more information to help troubleshooting.
	Enhanced `frame_too_large` and malformed CONNECT packet error logs to include more information to help troubleshooting.

Otherwise it may sound like the PR has improved failures.

[zmstone]

thanks. will fix in the next commit to come