Add the Suggest field to the SearchResp struct

[zr-bennettm]

Description

Adding the Explanation field to the

Issues Resolved

Closes issue #601

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

All modified and coverable lines are covered by tests ✅

Project coverage is 67.99%. Comparing base (06a6dc8) to head (679eaa7).
Report is 58 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff             @@
##             main     #602       +/-   ##
===========================================
+ Coverage   57.29%   67.99%   +10.70%     
===========================================
  Files         315      376       +61     
  Lines        9823     8862      -961     
===========================================
+ Hits         5628     6026      +398     
+ Misses       2902     1555     -1347     
+ Partials     1293     1281       -12     

Flag	Coverage Δ
integration	60.35% <ø> (+9.51%)	⬆️
unit	15.37% <ø> (+2.53%)	⬆️

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

Files	Coverage Δ
opensearchapi/api_search.go	100.00% <ø> (ø)

... and 272 files with indirect coverage changes

[dblock]

Thanks for this! I fixed integration tests in #600, FYI.

We also have #284 open. Would you mind please checking whether https://github.com/opensearch-project/opensearch-api-specification has this field and a test for it in https://github.com/opensearch-project/opensearch-api-specification/tree/main/tests, and if not maybe adding it? We want to make sure we don't introduce regressions when we replace this code with generated one (can use help on that too ;)).

[dblock]

See nit below.

Please rebase after #600? Thanks.

[zr-bennettm]

thanks for the quick approval @dblock ! Could I expect to see this be part of the next release (4.2)?

[dblock]

For sure. If you really, really need a release soon(er) open a "Release v. Next" issue and we'll take care of it.

(And if you do spend a little bit of time on my ask above for the API spec, it might happen faster ;)).