Auto Generated API - 3.0.0

[nhtruong]

Changed

• All API functions are now generated from the OpenSearch API specification.
• API request and response types are now generated from the OpenSearch API specification.
• Overhauled API codebase and break it into smaller, more manageable files for better readability and maintainability.

Removed

• BREAKING Removed support for API param aliases. That is, the API functions now only accept params with the exact names specified in the OpenSearch API specification.
• BREAKING Removed support for snake_cased API function names. All API functions are now camelCased only to conform to JavaScript naming conventions.
• BREAKING Removed support for Node.js 10 through 16. The minimum supported Node.js version is now 18.

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.

[dblock]

Let's branch 2.x before we merge this in order to have patch releases?

[dblock]

It's looking good.

I don't know how much we care, but a very large amount of files are changed for a 1-liner in the license header. Adding an extra * would reduce this PR by half I imagine.

Another though on the camelcase/snake case. Having to update all code from one method to the other is going to be a barrier for users even though it's mostly a trivial change. Would it make sense to consider also generating wrapper methods with the old names and marking them deprecated for another major version iteration? Or to generate a compatibility layer that can be optionally included?

[dblock]

Looking good. I tried to go through all the changes, made some suggestions in text.

I think after this is merged we should get another beta off main bofore releasing a final version. The final should be basically like the previous beta.

[nhtruong]

Looking good. I tried to go through all the changes, made some suggestions in text.

I think after this is merged we should get another beta off main bofore releasing a final version. The final should be basically like the previous beta.

I agree. There will be 2 follow-up PRs after this one:

• After the Search endpoint has been fixed in the spec, which I'm working on, I'll run the generator again to apply that change among others changes since the last time the spec was pulled to generate this. We can make a last beta release after that.
• Another PR for the generator code itself, and the supporting workflows. This can also wait till 3.1.0 release.

[dblock]

Nice work. Merge at will. The fact that samples don't have any changes in them is very encouraging.