style: Use gersemi instead of ancient cmake-format

[mathbunnyru]

cmake-format hasn't been updated in 5 years, and the styling is weird even with heavy customization.
gersemi looks nice, by default, with 0 configuration, and has been updated recently.

In my opinion it also just looks better.

High Level Overview of Change

Context of Change

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Refactor (non-breaking change that only restructures code)
• Performance (increase or change in throughput and/or latency)
• Tests (you added tests for code that already exists, or your new feature included in this PR)
• Documentation update
• Chore (no impact to binary, e.g. .gitignore, formatting, dropping support for older tooling)
• Release

API Impact

• Public API: New feature (new methods and/or new fields)
• Public API: Breaking change (in general, breaking changes should only impact the next api_version)
• libxrpl change (any change that may affect libxrpl or dependents of libxrpl)
• Peer protocol change (must be backward compatible or bump the peer protocol version)

[legleux]

I love it already

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 79.9%. Comparing base (dde4507) to head (af0ec7d).
⚠️ Report is 2 commits behind head on develop.

Additional details and impacted files

@@           Coverage Diff           @@
##           develop   #6486   +/-   ##
=======================================
  Coverage     79.8%   79.9%           
=======================================
  Files          861     861           
  Lines        67858   67858           
  Branches      7556    7553    -3     
=======================================
+ Hits         54167   54188   +21     
+ Misses       13691   13670   -21     

see 7 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.