Support warning and critical contacts in monitor body

[ojongerius]

Example of a template:

You can use monitor message template variables with the following syntax: {{var}}.
You can also use a simple if-else logic to show a message depending on the existence of a variable:
{{#var}} This text will show {{/var}}only if the variable `var` is true.
{{^var}} This text will show {{/var}}only if `var` is NOT true.

Examples:

Host {{host.name}} with IP {{host.ip}} is down.
{{#is_alert}} System disk usage is too high! {{/is_alert}}
{{^is_alert}} System disk usage is OK - but check dash 1234 just in case. {{/is_alert}}
The following variables are available for this monitor (given the selected scope):
is_alert, is_warning, is_recovery, is_no_data, is_match (for conditional statements )
process.name, host.autoscaling_group, host.availability-zone, host.aws-account-alias, host.buildinfo, host.builtfrom, host.business_unit, host.development, host.image, host.instance-type, host.ip, host.kernel, host.name, host.name_tag, host.power_nap, host.production, host.region, host.resource_owner, host.revision, host.security-group, host.service_name, host.staging

DoD:

Service checks can have different contacts for status changes to warning or critical.

[ojongerius]

Won't do.