Remove Hipchat support from Watcher (#39374)

* Remove Hipchat support from Watcher (#39199)

Hipchat has been shut down and has previously been deprecated in
Watcher (#39160), therefore we should remove support for these actions.

* Add migrate note

Author: dakrone

docs/reference/migration/migrate_7_0/plugins.asciidoc

@@ -75,3 +75,9 @@ Tribe node functionality has been removed in favor of
 
 * The method `DiscoveryPlugin#getDiscoveryTypes()` was removed, so that plugins
   can no longer provide their own discovery implementations.
+
+[float]
+==== Watcher 'hipchat' action removed
+
+Hipchat has been deprecated and shut down as a service. The `hipchat` action for
+watches has been removed.

docs/reference/settings/notification-settings.asciidoc

@@ -7,7 +7,6 @@
 
 You configure {watcher} settings to set up {watcher} and send notifications via
 <<email-notification-settings,email>>,
-<<hipchat-notification-settings,HipChat>>,
 <<slack-notification-settings,Slack>>, and
 <<pagerduty-notification-settings, PagerDuty>>.
 
@@ -67,10 +66,10 @@ Specifies the maximum size an HTTP response is allowed to have, defaults to
 
 `xpack.http.whitelist`::
 A list of URLs, that the internal HTTP client is allowed to connect to. This
-client is used in the HTTP input, the webhook, the slack, pagerduty, hipchat
+client is used in the HTTP input, the webhook, the slack, pagerduty,
 and jira actions. This setting can be updated dynamically.  It defaults to `*`
 allowing everything. Note: If you configure this setting and you are using one
-of the slack/pagerduty/hipchat actions, you have to ensure that the
+of the slack/pagerduty actions, you have to ensure that the
 corresponding endpoints are whitelisted as well.
 
 [[ssl-notification-settings]]
@@ -207,54 +206,6 @@ HTML feature groups>>.
 Set to `false` to completely disable HTML sanitation. Not recommended.
 Defaults to `true`.
 
-[float]
-[[hipchat-notification-settings]]
-==== HipChat Notification Settings
-You can configure the following HipChat notification settings in
-`elasticsearch.yml`. For more information about sending notifications
-via HipChat, see {xpack-ref}/actions-hipchat.html#configuring-hipchat-actions[Configuring HipChat].
-
-`xpack.notification.hipchat` ::
-Specifies account information for sending notifications
-via HipChat. You can specify the following HipChat account attributes:
-
-[[hipchat-account-attributes]]
-  `profile`;;
-  The HipChat account profile to use: `integration`,
-                      `user`, or `v1`. Required.
-
-  `secure_auth_token` (<<secure-settings,Secure>>);;
-  The authentication token to use to access the HipChat API. Required.
-
-  `host`;;
-  The HipChat server hostname. Defaults to `api.hipchat.com`.
-
-  `port`;;
-  The HipChat server port number. Defaults to 443.
-
-  `room`;;
-  The room you want to send messages to. Must be specified
-                      if the `profile` is set to `integration`. Not valid for
-                      the `user` or `vi` profiles.
-
-  `user`;;
-  The HipChat user account to use to send messages.
-                      Specified as an email address. Must be specified if the
-                      `profile` is set to `user`. Not valid for the `integration`
-                      or `v1` profiles.
-
-  `message.format`;;
-  The format of the message: `text` or `html`.
-                      Defaults to `html`.
-
-  `message.color`;;
-  The background color of the notification in the room.
-                      Defaults to  `yellow`.
-  `message.notify`;;
-  Indicates whether people in the room should be
-                      actively notified. Defaults to `false`.
-
-
 [float]
 [[slack-notification-settings]]
 ==== Slack Notification Settings

x-pack/docs/en/watcher/actions.asciidoc

@@ -16,8 +16,8 @@ serve as a model for a templated email body.
 
 {watcher} supports the following types of actions:
 <<actions-email, email>>, <<actions-webhook, webhook>>, <<actions-index, index>>,
-<<actions-logging, logging>>, <<actions-hipchat, hipchat>>, <<actions-slack,
-Slack>>, and <<actions-pagerduty, pagerduty>>.
+<<actions-logging, logging>>, <<actions-slack, Slack>>,
+and <<actions-pagerduty, pagerduty>>.
 
 [float]
 [[actions-ack-throttle]]
@@ -271,9 +271,6 @@ include::actions/index.asciidoc[]
 :edit_url: https://github.com/elastic/elasticsearch/edit/{branch}/x-pack/docs/en/watcher/actions/logging.asciidoc
 include::actions/logging.asciidoc[]
 
-:edit_url: https://github.com/elastic/elasticsearch/edit/{branch}/x-pack/docs/en/watcher/actions/hipchat.asciidoc
-include::actions/hipchat.asciidoc[]
-
 :edit_url: https://github.com/elastic/elasticsearch/edit/{branch}/x-pack/docs/en/watcher/actions/slack.asciidoc
 include::actions/slack.asciidoc[]
 
@@ -292,7 +289,7 @@ that even despite the exact same version, an OpenJDK distribution contains
 different parts under different Linux distributions.
 
 This can lead to issues with any action or input that uses TLS, like the `jira`,
-`pagerduty`, `slack`, `hipchat` or `webhook` one, because of missing CA certs.
+`pagerduty`, `slack`, or `webhook` one, because of missing CA certs.
 If you encounter TLS errors, when writing watches that connect to TLS endpoints,
 you should try to upgrade to the latest available OpenJDK distribution for your
 platform and if that does not help, try to upgrade to Oracle JDK.