Create/Update the workload to incorporate new match_only_text field

[rishabhmaurya]

Is your feature request related to a problem?

We have introduced a new match_only_text field type opensearch-project/OpenSearch#6836 and would like to incorporate it into one of the workload. This new field type is optimized for storage and trades off performance of positional queries like phrase query.

What solution would you like?

We can create a replica of PMC workload and use match_only_text field for all text fields.

What alternatives have you considered?

Creating a separate workload, which doesn't have the use case of positional queries but have use of full text search.

Do you have any additional context?

I ran some benchmarks earlier by modifying the field type locally to use match_only_text and here are the numbers -
opensearch-project/OpenSearch#6836 (comment)

[rishabhmaurya]

@gkamat what do you suggest here?

[gkamat]

@rishabhmaurya It may be helpful to create a new workload to exercise the nuances and capabilities of this new field. However, updating a workload like PMC to be able to run in a match_only_text mode via a workload parameter that is not the default would add to coverage of this feature as well.