Add check for latest Cadence 1.0 release

[jribbink]

Closes #1411

Description

Adds a check for latest cadence 1.0 release. We should remove this when feature/stable-cadence is merged into master, but if this is forgotten about, it shouldn't cause any issues either.

It's probably a good idea to have this so developers don't run into resolved issues since it's hard to track latest CLI versions/if you're using outdated CLI.

---

For contributor use:

• Targeted PR against master branch
• Linked to Github issue with discussion and accepted design OR link to spec that describes this work
• Code follows the standards mentioned here
• Updated relevant documentation
• Re-reviewed Files changed in the Github PR explorer
• Added appropriate labels

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 0% with 34 lines in your changes are missing coverage. Please review.

Project coverage is 41.62%. Comparing base (5c0fa11) to head (f59ae21).

❗ Current head f59ae21 differs from pull request most recent head c83c5bf. Consider uploading reports for the commit c83c5bf to get more accurate results

Files	Patch %	Lines
internal/command/command.go	0.00%	34 Missing ⚠️

Additional details and impacted files

@@                    Coverage Diff                     @@
##           feature/stable-cadence    #1496      +/-   ##
==========================================================
- Coverage                   41.99%   41.62%   -0.38%     
==========================================================
  Files                          59       59              
  Lines                        3360     3390      +30     
==========================================================
  Hits                         1411     1411              
- Misses                       1745     1775      +30     
  Partials                      204      204              

Flag	Coverage Δ
unittests	41.62% <0.00%> (-0.38%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

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