Fix auto managed index always have -2 seqNo bug

[bowenlan-amzn]

Issue #, if available:

Description of changes:

ISM has a function to auto manage the newly created index, however, we found in this path, the managed index created is always having policy seqNo set as -2, this is because the policy search request doesn't require seqNo back so it's always default to -2. This PR adds it back

CheckList:

• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[codecov]

Codecov Report

Merging #929 (8147743) into main (a2dd769) will increase coverage by 0.12%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##               main     #929      +/-   ##
============================================
+ Coverage     75.55%   75.68%   +0.12%     
- Complexity     2842     2846       +4     
============================================
  Files           364      364              
  Lines         16263    16263              
  Branches       2343     2343              
============================================
+ Hits          12288    12309      +21     
+ Misses         2626     2610      -16     
+ Partials       1349     1344       -5     

Files Changed	Coverage Δ
...nt/indexstatemanagement/ManagedIndexCoordinator.kt	71.18% <100.00%> (+2.08%)	⬆️
...t/action/indexpolicy/TransportIndexPolicyAction.kt	80.95% <100.00%> (ø)

... and 11 files with indirect coverage changes