Merge issues #89 and #101: Document Textual as implementation framework for IoT menu

[Copilot]

Description

Consolidates requirements from issues #89 (new Python-based iot menu) and #101 (auto-launch menu on environment start) into a unified development roadmap. Documents that Textual should be the implementation framework.

Related Issue

#89 #101

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update (changes to documentation)

Checklist

• My code follows the code style of this project.
• I have read the CONTRIBUTING.md document.
• I have checked that there are no other open pull requests for the same update/change.
• I have tested my changes and written tests when applicable.
• I have added necessary documentation (if appropriate).

Proposed Changes

• New doc/iot-menu-development.rst: Development roadmap consolidating both issues with:

  • Decision to use Textual (already in use in lib/ap_configurator/)
  • Rationale: consistent UI, modern TUI framework, SBC-friendly, Markdown support
  • Consolidated requirements from both issues
  • Implementation approach and related file references

• Updated bin/user_menu-python.py: Marked prompt_toolkit prototype as deprecated, pointing to Textual and the new roadmap

Additional Information

Textual is already a dependency (lib/iot_installs/requirements.txt) and used in lib/ap_configurator/, making it the natural choice for the new menu implementation.

Original prompt

Please merge issue #89 and #101 and explain that the work is to be done in textual.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.