[BUG] "Misspelling" on setting MaxAnalyzedOffset on IHighlight

[gjunge]

What is the bug?

Same bug as opensearch-project/opensearch-java#553 , since this part was copied from the ES clients. ES implemented this field as max_analyzed_offset (see ES docs), while OpenSearch implemented the field as max_analyzer_offset in 2.2.0 (see OS docs)

As can be seen in the Java client bug description, using this field will lead to this error

    "error": {
        "root_cause": [
            {
                "type": "x_content_parse_exception",
                "reason": "[36:9] [highlight] unknown field [max_analyzed_offset] did you mean [max_analyzer_offset]?"
            }
        ],
        "type": "x_content_parse_exception",
        "reason": "[36:9] [highlight] unknown field [max_analyzed_offset] did you mean [max_analyzer_offset]?"
    },
    "status": 400
}

How can one reproduce the bug?

var results = await _opensearchClient.SearchAsync<MyRecord>(
        sd => sd.TrackTotalHits(true)
                .Query(q => q.MatchAll())
                .Highlight(h =>
                h.PreTags("<mark>")
                    .PostTags("</mark>")
                    .Fields(
                        f => f.Field("title")
                    )
                    .MaxAnalyzedOffset(10000)  //<-- this is the issue.
                )


        );

What is the expected behavior?

Update the api to match the OpenSearch Highlight setting max_analyzer_offset

What is your host/environment?

AWS Managed OpenSearch service 2.7.