Kibana's Console displays misleading message when no response body is returned

[n0othing]

Kibana version: 8.14.3

Elasticsearch version: 8.14.3

Describe the bug:

Kibana's Console can display a misleading message when a request only returns a status code. For example, a successful call to Elasticsearch's voting exclusion API (see here) causes Console to display Request failed to get to the server (status code: 200).

Steps to reproduce:

1.) Create a simple 3x node cluster (all master eligible nodes) and attempt to exclude one of the nodes via Kibana's Console:

# node-a
node.name: node-a
http.port: 9200
transport.port: 9300
cluster.initial_master_nodes: ["127.0.0.1:9300", "127.0.0.1:9301", "127.0.0.1:9302" ]
discovery.seed_hosts: ["127.0.0.1:9300", "127.0.0.1:9301", "127.0.0.1:9302" ]
xpack.security.enabled: false
xpack.license.self_generated.type: trial
ingest.geoip.downloader.enabled: false
node.roles: [ master, data_content, data_hot ]

# node-b
node.name: node-b
http.port: 9201
transport.port: 9301
cluster.initial_master_nodes: ["127.0.0.1:9300", "127.0.0.1:9301", "127.0.0.1:9302" ]
discovery.seed_hosts: ["127.0.0.1:9300", "127.0.0.1:9301", "127.0.0.1:9302" ]
xpack.security.enabled: false
xpack.license.self_generated.type: trial
ingest.geoip.downloader.enabled: false
node.roles: [ master, data_content, data_hot ]

# node-c
node.name: node-c
http.port: 9202
transport.port: 9302
cluster.initial_master_nodes: ["127.0.0.1:9300", "127.0.0.1:9301", "127.0.0.1:9302" ]
discovery.seed_hosts: ["127.0.0.1:9300", "127.0.0.1:9301", "127.0.0.1:9302" ]
xpack.security.enabled: false
xpack.license.self_generated.type: trial
ingest.geoip.downloader.enabled: false
node.roles: [ master, data_content, data_hot ]

POST /_cluster/voting_config_exclusions?node_names=node-a

Expected behavior:

Ideally, Kibana should interpret the 200 response code as a success.

Screenshots (if relevant):

[elasticmachine]

Pinging @elastic/kibana-management (Team:Kibana Management)