feat: increase command limit to 100 and add optimization guide

Changes:
- Increase command limit from 50 to 100 per project
- Add examples/OPTIMIZE_CONFIG.md with optimization strategies
- Update all documentation references (50 → 100)
- Update tests for new limit

Rationale:
- 50 was too restrictive for projects with many tools (Flutter, etc.)
- Users were unknowingly exceeding limit by listing subcommands
- 100 provides headroom while maintaining security
- New guide teaches wildcard optimization (flutter* vs listing each subcommand)

UI feedback idea: Show command count and optimization suggestions
(tracked for Phase 3 or future enhancement)

examples/project_allowed_commands.yaml

@@ -113,7 +113,7 @@ commands: []
 #   - Scripts: "./scripts/build.sh" matches the script by name
 #
 # Limits:
-#   - Maximum 50 commands per project
+#   - Maximum 100 commands per project
 #   - Commands in the blocklist (sudo, dd, shutdown, etc.) can NEVER be allowed
 #   - Org-level blocked commands (see ~/.autocoder/config.yaml) cannot be overridden
 #