Test against OpenSearch 1.3.17.

[dblock]

Description

This passes tests against OpenSearch 1.x.

Since 1.x is still supported I think we should also support it in the spec. Clients can choose to ignore anything that's x-version-removed=2.0. This gives us a way to evolve backwards incompatible changes in 3.0.

The other option is a 1.x branch and we can have backports. It's possibly easier, and so if you think it's better, then I can PR spec and tests with >= 2.0 separately so that the diff is smaller, and make a 1.x branch.

WDYT @nhtruong @Xtansia ?

Issues Resolved

Part of #84.

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.

[github-actions]

Changes Analysis

Commit SHA: 7476fae
Comparing To SHA: 9c15bbf

API Changes

Summary

└─┬Components
  ├──[➕] schemas (27929:7)
  ├─┬_core.search:Hit
  │ └──[➕] properties (37978:9)
  ├─┬_common:WriteResponseBase
  │ └──[➕] properties (28011:9)
  ├─┬cat.health:HealthRecord
  │ └──[➕] properties (38813:9)
  ├─┬_core.get:GetResult
  │ └──[➕] properties (36893:9)
  └─┬_core.bulk:ResponseItem
    └──[➕] properties (36667:9)

Document Element	Total Changes	Breaking Changes
components	6	0

• Total Changes: 6
• Additions: 6

Report

The full API changes report is available at: https://github.com/opensearch-project/opensearch-api-specification/actions/runs/9960862929/artifacts/1707284013

API Coverage

	Before	After	Δ
Covered (%)	483 (47.31 %)	483 (47.31 %)	0 (0 %)
Uncovered (%)	538 (52.69 %)	538 (52.69 %)	0 (0 %)
Unknown	24	24	0

[nhtruong]

This is fine. The changes between major versions we see now are mainly adding and removing components so this works.
We'll split 1x into its own branch once it becomes a burden. Right now we're still adding more features for the tools and tests into the spec, so we should wait awhile before making 1x branch or we will have to backport a lot.