Add interactive mode

[DenysKuchma]

Summary

This PR adds an interactive mode to doc-collector so page documentation can include verified UI behavior, not just static page structure.
The new mode explores selected interactions, captures state changes, and falls back safely to static documentation when interactive results are weak or unreliable.

What changed

• added opt-in interactive mode for doc-collector
• added deterministic interaction exploration for:
• content/detail links
• pagination
• tab-like controls
• meaningful buttons
• added State Transitions output in page docs using a before -> action -> after format
• added support for carrying interaction-discovered URLs into the crawl queue
• added output normalization and coverage notes for weak or partial documentation
• improved fallback behavior when interactive or schema generation fails
• cleaned up the interactive implementation and removed legacy / dead code paths

[DavertMik]

Same for new features too.
See CLAUDE.md

Regexes are fine for some quick wins but evaluating actions by categories is what LLM must do (it does it well). If a solution involves Regex - probably it is not a solution. It might be optimization but not a solution!