[DOC] Concurrent Segment Search is disabled in terminate_after workflow

[jed326]

What do you want to do?

• Request a change to existing documentation
• Add new documentation
• Report a technical problem with the documentation
• Other

Tell us about your request. Provide a summary of the request and all versions that are affected.
Sample proposed wording:
For concurrent segment search we are disabling concurrent segment search when the terminate_after parameter is used. With terminate_after we typically expect the queries to be used with smaller values and thus complete very quickly as this effectively reduces the dataset size on which search is done, so concurrent search may not really help with such cases. Moreover, due to added complexity when used with other search request parameters including track_total_hits and size, the behavior changes with terminate_after after therefore we are falling back to non-concurrent path for these search requests to ensure consistent results between concurrent and non-concurrent requests.

Affected section: https://github.com/opensearch-project/documentation-website/blob/main/_search-plugins/concurrent-segment-search.md#the-terminate_after-search-parameter

What other resources are available? Provide links to related issues, POCs, steps for testing, etc.
opensearch-project/OpenSearch#10200