Feature: New Class MacAddress similar to IPAddress

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

Description of Change

This adds new class MacAddress that allows for better handling of MAC and BSSID addresses.
MacAddress also support 8-byte EUI-64 as noted in esp_mac.h.

Changes have been done on top of @mrengineer7777 PR #6667. Thanks David!

Tests scenarios

Tested by running slightly modified test sketch by @mrengineer7777.
https://gist.github.com/P-R-O-C-H-Y/ab6b2443fc57bc12ec424f89493b9022

Related links

Closes #6658

[github-actions]

	Warnings
⚠️	Some issues found for the commit messages in this PR: the commit message "Added Printable": summary looks empty type/action looks empty the commit message "Added Printable, constructor and extra operators": summary looks empty type/action looks empty the commit message "Added Printble and some more operators": summary looks empty type/action looks empty the commit message "Added construtor and Printable": summary looks empty type/action looks empty the commit message "Added new classes MacAddress and MacAddress8": summary looks empty type/action looks empty the commit message "Cleanup and bounds checking": body's lines must not be longer than 100 characters summary looks empty type/action looks empty the commit message "Fix buffer size for toString": summary looks empty type/action looks empty the commit message "Fixed printTo": summary looks empty type/action looks empty the commit message "Fixes include Printable": summary looks empty type/action looks empty the commit message "Update MacAddress.cpp": summary looks empty type/action looks empty the commit message "Update MacAddress.cpp": summary looks empty type/action looks empty the commit message "Update MacAddress.h": summary looks empty type/action looks empty the commit message "Update MacAddress8.h": summary looks empty type/action looks empty the commit message "Update toString function with single buf and return": summary looks empty type/action looks empty the commit message "feat(MAC): Remove MacAddress8.h file": scope/component should be lowercase without whitespace, allowed special characters are _ / . , * - . the commit message "feat(MAC): Rework API to support both 6+8 bytes MacAddress": scope/component should be lowercase without whitespace, allowed special characters are _ / . , * - . the commit message "fix(MAC): Remove comment + reorder lines": scope/component should be lowercase without whitespace, allowed special characters are _ / . , * - . Please fix these commit messages - here are some basic tips: follow Conventional Commits style correct format of commit message should be: <type/action>(<scope/component>): <summary>, for example fix(esp32): Fixed startup timeout issue allowed types are: change,ci,docs,feat,fix,refactor,remove,revert,test sufficiently descriptive message summary should be between 20 to 72 characters and start with upper case letter avoid Jira references in commit messages (unavailable/irrelevant for our customers) TIP: Install pre-commit hooks and run this check when committing (uses the Conventional Precommit Linter).
⚠️	Please consider squashing your 23 commits (simplifying branch history).

👋 Hello P-R-O-C-H-Y, we appreciate your contribution to 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.
- Resolve all warnings (⚠️ ) before requesting a review from human reviewers - they will appreciate it.
- 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 df8c70c

[lucasssvaz]

LGTM

[me-no-dev]

@mrengineer7777 will you chime in to say if you are OK with this PR?

[lucasssvaz]

@P-R-O-C-H-Y Could you add a simple example sketch ? (A very basic one is enough IMO)