feat(ap): Add support for DHCP Captive Portal (opt 114)

[me-no-dev]

This pull request introduces functionality to enable a DHCP-based captive portal for WiFi access points, along with updates to simplify the setup process in the Captive Portal example. The most significant changes include adding the new enableDhcpCaptivePortal method to the APClass, modifying the example code to utilize this new feature, and updating the WiFiAP.h header file to declare the new method.

Enhancements to WiFi Access Point functionality:

• Added enableDhcpCaptivePortal method to APClass: This method enables a DHCP-based captive portal by configuring the DHCP server to redirect clients to a specific captive portal URI. It includes error handling for stopping and starting the DHCP server and checks if the access point is started before enabling the feature.
• Declared enableDhcpCaptivePortal in WiFiAP.h: The new method is added to the APClass interface, making it accessible for users of the library.

Updates to the Captive Portal example:

• Simplified WiFi setup in CaptivePortal.ino: Replaced the manual configuration of the access point with the new WiFi.AP.create and WiFi.AP.enableDhcpCaptivePortal methods, streamlining the setup process for users.

Closes #11399

[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 711ca88

[github-actions]

Test Results

 76 files   76 suites   12m 45s ⏱️
 38 tests  38 ✅ 0 💤 0 ❌
241 runs  241 ✅ 0 💤 0 ❌

Results for commit 711ca88.

♻️ This comment has been updated with latest results.