fix AMMClawback vote behavior to default NO

[yinyiqian1]

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)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 77.7%. Comparing base (c5c0e70) to head (ab77a92).
Report is 1 commits behind head on develop.

Additional details and impacted files

@@           Coverage Diff           @@
##           develop   #5181   +/-   ##
=======================================
  Coverage     77.7%   77.7%           
=======================================
  Files          779     779           
  Lines        66015   66016    +1     
  Branches      8156    8152    -4     
=======================================
+ Hits         51261   51270    +9     
+ Misses       14754   14746    -8     

see 4 files with indirect coverage changes

[mvadari]

This was rolled into #5103 so is no longer needed as a separate PR.