[DOC] Add query parameter support to terms lookup table in Terms Query documentation

[srikanthpadakanti]

Description

This PR updates the Terms Query documentation to reflect the enhancement for terms lookup queries to support the query parameter, as described in opensearch-project/OpenSearch#17599.

• Adds the query parameter to the terms lookup parameters table.
• Clarifies the usage of id vs. query for terms lookup.
• Prepares documentation for the upcoming feature release.

Issues Resolved

Closes #10526
Linked to opensearch-project/OpenSearch#17599

Version

To be released in the 3.2 version

Checklist

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

[github-actions]

Thank you for submitting your PR. The PR states are In progress (or Draft) -> Tech review -> Doc review -> Editorial review -> Merged.

Before you submit your PR for doc review, make sure the content is technically accurate. If you need help finding a tech reviewer, tag a maintainer.

When you're ready for doc review, tag the assignee of this PR. The doc reviewer may push edits to the PR directly or leave comments and editorial suggestions for you to address (let us know in a comment if you have a preference). The doc reviewer will arrange for an editorial review.

[kolchfa-aws]

Thank you, @srikanthpadakanti! I edited the docs. Can you please add a complete example:

• The users index setup
• The response received from the terms lookup by query
  Also, instead of the 3 examples (missing fields, field specified as scalar and list, and empty/null fields), it would be great to provide an actual request that has all 3 and the response. We can then explain the response and show the behavior.

[srikanthpadakanti]

Thank you, @srikanthpadakanti! I edited the docs. Can you please add a complete example:

• The users index setup
• The response received from the terms lookup by query
  Also, instead of the 3 examples (missing fields, field specified as scalar and list, and empty/null fields), it would be great to provide an actual request that has all 3 and the response. We can then explain the response and show the behavior.

@kolchfa-aws I have added full example covering the edge cases as well.

[natebower]

Editorial review

[natebower]

LGTM