feat: add FAQ section and enhance documentation

[meenu155]

• Added a new FAQ page with comprehensive answers to common questions.
• Updated the main documentation to include new features and improvements.
• Enhanced the getting started guide with hot reload and admin dashboard instructions.
• Introduced a troubleshooting guide covering installation, development, Docker, and service-specific issues.
• Improved the index page with a detailed overview of features and quick start instructions.
• Updated the Vitepress configuration to include the new FAQ link and additional sidebar items.

Summary

Explain the change in 1–3 sentences. Reference any related issues (e.g. Closes #123).

Type of Change

• 🚀 Feature (feat:) - New functionality for users
• 🐛 Bug fix (fix:) - Fixes an issue for users
• ⚠️ Breaking Change (feat!: or fix!:) - Changes that break backward compatibility
• 📚 Docs (docs:) - Documentation updates only
• 🔧 Chore / Refactor (chore:, refactor:) - Internal changes, no user impact
• 🧪 Tests (test:) - Test additions or updates
• 🚀 CI / Build (ci:) - Build system or CI changes
• 📦 Dependencies (deps:) - Dependency updates
• 🎉 Other - Changes that don't fit the above categories

Release Notes Impact

• User-facing change - Should be included in release notes
• Internal change only - No need to include in release notes

Motivation / Context

Why is this change needed? What problem does it solve or what capability does it add?

Approach

Briefly describe how you implemented the change. Note any notable design decisions, trade-offs, or alternatives considered.

CLI Impact

If this alters user-facing CLI behavior:

• Added / changed flags? Describe.
• Backward compatible? If breaking, explain migration path.
• Sample invocation before vs after:

# before
# after

Generated Output Impact

List any new / modified scaffold files or structural differences (e.g. new template folder, changed Dockerfile pattern, compose changes, new preset behaviors).

Tests

Describe test coverage:

• Added new test(s)
• Updated existing test(s)
• Manually smoke-tested locally
• No tests needed (explain why)

If you ran the smoke scaffold locally, paste the command & confirm success:

node bin/index.js demo --services node --no-install --yes

Result: ✅ / ❌

Breaking Changes & Migration

Breaking changes:

Migration steps:

Configuration changes needed:

Screenshots / Logs (Optional)

Add any helpful output (chalk-styled CLI messages, error reproduction, etc.).

Docs

• Updated README.md if needed
• Updated .github/copilot-instructions.md if internal conventions changed
• Added/updated relevant documentation for user-facing changes
• Not applicable

Checklist

• Code follows existing style (chalk usage, emoji prefixes, exit codes)
• No accidental large asset additions outside templates/
• Default ports preserved / conflicts handled
• New service templates added to: choices array, defaultPorts, Dockerfile switch, compose mapping
• Git history clean (no stray debug commits)
• Dependency additions are minimal & justified

Open Questions / Follow-ups

List any TODOs or future enhancements not in this PR.

---

Thanks for contributing! 🎉