Remove deprecated API that uses non-inclusive terminology

[tlfeng]

Is your feature request related to a problem? Please describe.
All the REST API and Java that uses non-inclusive terminology master and blacklist/whitelist have been deprecated in version 2.0 - 2.2, and will be removed in version 3.0
This issue aims to track the effort of deprecated API removal that related to inclusive naming project.

REST API:

• _cat/master API
• master_timeout request parameter
• "master" node role in _cat/nodes API

Cluster Settings:

• cluster.initial_master_nodes
• cluster.no_master_block
• node.master

(done) Java API:

• [BUG] Remove package org.opensearch.action.support.master #4856 package o.o.action.support.master
• Replace "master" terminology in Java APIs #1684

Additional context
A part of #2773 - List of deprecated code removal for v3.0
A part of #3351 - Breaking changes in 3.0

[andrross]

As of now, we have removed all usages of non-inclusive terms from the Java APIs. This has cleaned up almost all of the legacy cruft in terms of duplicate and/or deprecated code. What remains is the 3 cluster settings, a couple REST APIs, and one REST query parameter. While we have done most of the work to remove the non-inclusive terms, I'm proposing that we defer the removal of these last user-facing names until 4.0. I know clients can be the hardest thing to update, so the tradeoff to weigh here is the additional friction these removals might cause versus the cost of carrying these deprecations for one more major version. I think this is a case where it may be prudent to carry the deprecation for another major version just to be extra conservative.