feat: unify pipeline session creation between analyze and run commands

[omsherikar]

Summary

refactron run uses RefactronPipeline.analyze (which saves a session) and sets current session. refactron analyze builds a separate PipelineSession inline, queues all issues, saves, and sets current — overlapping responsibilities with different code paths and risk of drift (fields, defaults, future flags).

Suggested direction

• Extract a single helper e.g. create_session_from_analysis(result, target, ...) used by both CLI and RefactronPipeline.
• Ensure issues_by_level, fix queue policy, and state transitions stay consistent.

Acceptance

• One code path for “analysis result → persisted session” for connected commands.
• Tests updated; behavior unchanged for users.

Code

• refactron/core/pipeline.py
• refactron/cli/analysis.py
• refactron/cli/run.py

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity for 30 days.

If you believe this issue is still relevant, please:

• Add a comment explaining why
• Remove the stale label
• Or simply comment to keep it active

This helps us keep the repository focused on active issues. Thank you for your contribution! 🙏