[META] Add support for inclusive naming for all clients

[saratvemulapalli]

Is your feature request related to a problem?
Starting with OpenSearch 2.0, we are moving to support inclusive naming across the project.
Ref:
[1] opensearch-project/OpenSearch#472
cc: @tlfeng

Coming from: opensearch-project/opensearch-py#156 (comment)

What solution would you like?
Add support to new inclusive REST API usages.
Change any internal REST API calls (which don't face to user) to use new inclusive usages, instead of the old REST APIs that contain "master" terminology. Otherwise, using REST API usages with "master" word will lead to deprecation warning emitted from OpenSearch server.
Additional Context:
The REST API and setting changes about "master" terminology:
opensearch-project/documentation-website#450

The setting change about "blacklist / whitelist" terminology:
opensearch-project/documentation-website#449

Note: The REST API parameter "master_timeout" is not deprecated in 2.0 (but in 3.0) to keep the compatibility of OpenSearch "High Level REST Client" with server version 1.x (See the issue opensearch-project/OpenSearch#2928 for detail)

Tracking changes in clients

• opensearch-java - [FEATURE] Add support for inclusive naming opensearch-java#166
• opensearch-ruby - [FEATURE] Add support for inclusive naming opensearch-ruby#72
• opensearch-php - [FEATURE] Add support for inclusive naming opensearch-php#61
• opensearch-js - Deprecate the "Master" nomenclature in nodejs client opensearch-js#221
• opensearch-dsl-py - [FEATURE] Add support for inclusive naming opensearch-dsl-py#60
• opensearch-go - [FEATURE] Add support for inclusive naming opensearch-go#121
• opensearch-rs - [FEATURE] Add support for inclusive naming opensearch-rs#56
• opensearch-py - [FEATURE] Add support for inclusive naming opensearch-py#174
• opensearch-net - [FEATURE] Add support for inclusive naming opensearch-net#89

[tlfeng]

You could feel free to add the following to the top ^ 😁 :

Suggested solution:

1. Add support to new inclusive REST API usages.
2. Change any internal REST API calls (which don't face to user) to use new inclusive usages, instead of the old REST APIs that contain "master" terminology. Otherwise, using REST API usages with "master" word will lead to deprecation warning emitted from OpenSearch server.

Additional Context:
The REST API and setting changes about "master" terminology:
opensearch-project/documentation-website#450

The setting change about "blacklist / whitelist" terminology:
opensearch-project/documentation-website#449

Note: The REST API parameter "master_timeout" is not deprecated in 2.0 (but in 3.0) to keep the compatibility of OpenSearch "High Level REST Client" with server version 1.x (See the issue opensearch-project/OpenSearch#2928 for detail)

[saratvemulapalli]

JS: opensearch-project/opensearch-js#224

[VachaShah]

Thank you @saratvemulapalli for opening this! Converting this into a meta issue to track the changes for various clients.

[VachaShah]

Closing this issue since all existing clients support inclusive naming.