Support PagerDuty v2 as part of Kapacitor v1.5 update

[timhallinflux]

Kapacitor v1.5 will support PagerDuty v2 interface. There are some changes required in terms of the parameters to configure this. Chronograf should support the PagerDuty v2 setup -- and prep for PagerDuty v1 deprecation by Kapacitor v1.6.

Please see: influxdata/kapacitor#1795

• leverage the services endpoint to determine what configs are available
• only show the configs that are returned from the services endpoint in alertTabs
• add a pagerduty v2 config option to the Kapacitor config option of chronograf
• add a deprecation warning to the UI for pagerduty v1 so users know they will need to update
• update kapacitor dependency to v1.5

[nhaugo]

@timhallinflux is pagerduty finally removing support for v1? If not I don't know why we would replace v1 this instead of just adding v2.

[russorat]

@nhaugo

https://v2.developer.pagerduty.com/v2/docs/v1-rest-api-decommissioning-faq

WHAT’S HAPPENING?
On April 24, 2018, at 22:00 PDT (UTC+7), our v1 REST API is entering a decommissioning period. Starting on that date, you will no longer be able to generate v1 REST API keys, but the v1 REST API will remain operational.

On October 19, 2018, at 22:00 PDT (UTC+7), the v1 REST API will be decommissioned and no longer operational.

[russorat]

1.5rc1 is out so lets test and verify with that: https://github.com/influxdata/kapacitor/releases/tag/v1.5.0-rc1

[russorat]

• the line should start with "PagerDuty v1 is being deprecated... "

[russorat]

this is working. thanks!!!

[russorat]

in rc2, the service-key config has been updated to be routing-key. we will need to update this.

Also, let's display the error returned when trying to configure this:

also if you need to delete service-key from your config, you can use this: curl -XPOST http://localhost:9092/kapacitor/v1/config/pagerduty2/ -d '{"delete":["service-key"]}'

[jaredscheib]

I've fixed the error display bug (#3385) in #3386.