feat(udp): Allow for packets up to 1460 bytes

[me-no-dev]

This pull request updates the maximum segment size configuration for UDP operations in the AsyncUDP.cpp file. The changes ensure that UDP-related buffer allocations and data transmissions use the correct maximum segment size constant, improving protocol correctness and maintainability.

Configuration updates:

• Added a new constant definition for CONFIG_UDP_MSS set to 1460 to specify the maximum segment size for UDP.
• Updated buffer allocation logic in the AsyncUDPMessage constructor to use CONFIG_UDP_MSS instead of CONFIG_TCP_MSS, ensuring UDP messages do not exceed the appropriate segment size.
• Modified the AsyncUDP::writeTo method to use CONFIG_UDP_MSS for limiting the length of outgoing UDP packets, replacing the previous use of CONFIG_TCP_MSS.

Fixes: #12162

[github-actions]

	Messages
📖	🎉 Good Job! All checks are passing!

👋 Hello me-no-dev, we appreciate your contribution to this project!

---

📘 Please review the project's Contributions Guide for key guidelines on code, documentation, testing, and more.

---

🖊️ Please also make sure you have read and signed the Contributor License Agreement for this project.

---

Click to see more instructions ...

This automated output is generated by the PR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with each push event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger is not a substitute for human code reviews; it's still important to request a code review from your colleagues.
- To manually retry these Danger checks, please navigate to the Actions tab and re-run last Danger workflow.

Review and merge process you can expect ...

We do welcome contributions in the form of bug reports, feature requests and pull requests.

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
4. If the change is approved and passes the tests it is merged into the default branch.

Generated by 🚫 dangerJS against 6de21b5

[github-actions]

Memory usage test (comparing PR against master branch)

The table below shows the summary of memory usage change (decrease - increase) in bytes and percentage for each target.

Memory	FLASH [bytes]		FLASH [%]		RAM [bytes]		RAM [%]
Target	DEC	INC	DEC	INC	DEC	INC	DEC	INC
ESP32	0	0	0.00	0.00	0	0	0.00	0.00
ESP32C3	0	0	0.00	0.00	0	0	0.00	0.00
ESP32C5	0	0	0.00	0.00	0	0	0.00	0.00
ESP32C6	0	0	0.00	0.00	0	0	0.00	0.00
ESP32P4	0	0	0.00	0.00	0	0	0.00	0.00
ESP32S2	0	0	0.00	0.00	0	0	0.00	0.00
ESP32S3	0	0	0.00	0.00	0	0	0.00	0.00

Click to expand the detailed deltas report [usage change in BYTES]

Target	ESP32		ESP32C3		ESP32C5		ESP32C6		ESP32P4		ESP32S2		ESP32S3
Example	FLASH	RAM	FLASH	RAM	FLASH	RAM	FLASH	RAM	FLASH	RAM	FLASH	RAM	FLASH	RAM
libraries/AsyncUDP/examples/AsyncUDPClient	0	0	0	0	0	0	0	0	0	0	0	0	0	0
libraries/AsyncUDP/examples/AsyncUDPMulticastServer	0	0	0	0	0	0	0	0	0	0	0	0	0	0
libraries/AsyncUDP/examples/AsyncUDPServer	0	0	0	0	-	-	0	0	0	0	0	0	0	0
libraries/DNSServer/examples/CaptivePortal	0	0	0	0	-	-	-	-	0	0	0	0	-	-
libraries/NetBIOS/examples/ESP_NBNST	0	0	0	0	-	-	-	-	0	0	0	0	-	-
libraries/Update/examples/HTTP_Server_AES_OTA_Update	0	0	0	0	-	-	-	-	0	0	0	0	-	-

[P-R-O-C-H-Y]

LGTM

[github-actions]

Test Results

 90 files   90 suites   32m 28s ⏱️
 67 tests  61 ✅ 0 💤 6 ❌
751 runs  744 ✅ 0 💤 7 ❌

For more details on these failures, see this check.

Results for commit 6de21b5.

♻️ This comment has been updated with latest results.

[lucasssvaz]

LGTM