fix(example): Update GetMacddress.ino for 8 and 2 byte MACs

[me-no-dev]

This pull request enhances the GetMacAddress example for ESP32 by adding support for devices that include IEEE 802.15.4 (Thread/Zigbee) and external MAC addresses, and by updating the code to handle both 6-byte and 8-byte MAC addresses when relevant. The changes ensure the example works correctly on more ESP32 variants and displays the correct MAC address format depending on the interface.

Support for additional MAC address types and formats:

• Updated the output header in setup() to clarify that MAC addresses may be 6 or 8 bytes, reflecting the new interface support.
• Added conditional code to print IEEE802154 and EXT MAC addresses if the platform supports IEEE 802.15.4, using esp_read_mac for these interfaces.

Generalization for variable MAC address lengths:

• Modified the getDefaultMacAddress() and getInterfaceMacAddress() functions to use 8-byte buffers and dynamically format either 6-byte or 8-byte MAC addresses, depending on the interface and configuration. [1] [2]

Fixes: #12255

[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 f2264f7

[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	💚 -4	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
ESP32H2	0	⚠️ +298	0.00	⚠️ +0.11	0	0	0.00	0.00
ESP32P4	💚 -4	0	0.00	0.00	0	0	0.00	0.00
ESP32S2	💚 -4	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		ESP32H2		ESP32P4		ESP32S2		ESP32S3
Example	FLASH	RAM	FLASH	RAM	FLASH	RAM	FLASH	RAM	FLASH	RAM	FLASH	RAM	FLASH	RAM	FLASH	RAM
libraries/ESP32/examples/MacAddress/GetMacAddress	0	0	💚 -4	0	-	-	-	-	⚠️ +298	0	💚 -4	0	💚 -4	0	-	-