feat: explore “app store” style installation experience

Summary

Investigate what it would take to provide an "app store"-like installation flow for MagicMirror² modules so that users can install modules with a single click and receive a basic configuration stub automatically.

Motivation

• Simplify module discovery-to-install pipeline for end users.
• Reduce friction when setting up mirrors, especially for newcomers who are not comfortable with command line workflows.

Open questions

• What backend or command tooling would orchestrate installs (e.g. integration with npm, custom CLI, or a hosted service)?
• How would configuration defaults be provided and merged with existing config.js setups safely?
• What UX changes would the modules listing site need (authentication, queueing installs, progress feedback)?
• Which security and permission considerations (e.g. verifying module sources) must be addressed first?

Next steps

• Collect prior art (MMM-Remote-Control, mmpm, MMM-Config ,other smart mirror ecosystems).
• Outline possible architectures (pure UI + docs, downloadable helper app, hosted service, etc.).
• Identify blockers and resource requirements before committing to an implementation roadmap.

Start by reviewing the modules listing site and the prior art named in the issue: MMM-Remote-Control, mmpm, and MMM-Config. Compare the proposed UI, helper-app, and hosted-service approaches, including npm or CLI orchestration, configuration merging, authentication, progress feedback, and source verification; done means a documented architecture comparison, blockers, and resource requirements.