setup_project_repos prints the repo-targets table twice

puppetsync::setup_project_repos emits the repo-targets summary table twice at session start:

out::message(puppetsync::summarize_repo_targets($repos))
warning(puppetsync::summarize_repo_targets($repos,true))

Once plain via out::message and once colorized via warning() — and since Bolt's default console level shows warnings, both render in every run.

Fix: keep one (probably the colorized out::message form, matching how output_pipeline_results renders the results table) and drop the other.

Not to be confused with the whole-output doubling under --log-level info: that one is Bolt behavior (out::message prints directly to the console and emits an info-level log event, so raising the console level to info renders everything twice) — reproduced 1× at default vs 2× at info on a minimal fixture; nothing puppetsync can cleanly do about it, and it only occurs when verbose output was explicitly requested.

Cosmetic; fine to fold into whatever PR next touches setup_project_repos.pp rather than fixing standalone.

🤖 Generated with Claude Code

Start in setup_project_repos.pp and compare its repo-targets output with the rendering used by output_pipeline_results. Confirm the session-start summary is emitted only once, then run the relevant project checks or fixture to verify the duplicate table is gone.