chore(cli): mark sync-v1 and bridge as unsafe

[jansegre]

Motivation

We're at a point where every node is running only sync-v2, except for a few nodes that we maintain in bridge mode that run sync-v1 + sync-v2. So for the next release we can safely disincentivize sync-v1 from being used either through --sync-v1-only or --sync-bridge.

Acceptance Criteria

• hide --sync-bridge, mark it as unsafe and unhide --x-sync-bridge (also unsafe) to be used instead
• hide --sync-v1-only, mark it as unsafe and add --x-sync-v1-only (also unsafe) to be used instead
• hide --sync-v2-only, since it's the default, using it will only show a warning
• after the above, every cli option that enables sync-v1 should require --unsafe=... to be used

Checklist

• If you are requesting a merge into master, confirm this code is production-ready and can be included in future releases as soon as it gets merged

[codecov]

Codecov Report

Attention: Patch coverage is 57.14286% with 3 lines in your changes missing coverage. Please review.

Project coverage is 84.86%. Comparing base (631f2ca) to head (a8de807).
Report is 2 commits behind head on master.

Files	Patch %	Lines
hathor/builder/cli_builder.py	57.14%	2 Missing and 1 partial ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1090   +/-   ##
=======================================
  Coverage   84.86%   84.86%           
=======================================
  Files         314      314           
  Lines       23898    23905    +7     
  Branches     3611     3613    +2     
=======================================
+ Hits        20280    20286    +6     
  Misses       2906     2906           
- Partials      712      713    +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.