Increase time between two check_mk_agent runs

right now, check_mk_agent is run every minute on each host. The soledad sync test depends on tapicero, and in "between finishing the soledad test and removing the testuser db, and the start of another test there's only 13s":https://leap.se/code/issues/6537#note-2

we should run check_mk_agent at least every 2 minutes.

# Template used by all other check_mk templates
define service {
  name                            check_mk_default
  register                        0
  active_checks_enabled           1
  passive_checks_enabled          1
  parallelize_check               1
  obsess_over_service             1
  check_freshness                 0
  notifications_enabled           1
  event_handler_enabled           0
  flap_detection_enabled          1
  failure_prediction_enabled      1
  process_perf_data               0
  retain_status_information       1
  retain_nonstatus_information    1
  notification_interval           0
  is_volatile                     0
  normal_check_interval           1
  retry_check_interval            1
  max_check_attempts              1
  notification_options            u,c,w,r,f,s
  notification_period             24X7
  check_period                    24X7
}

# This template is used by the service that actively
# calls check_mk. Each host has exactly one service
# using this template. Here you can configure, how often
# each host should be checked.
define service {
  name                            check_mk_active
  use                             check_mk_perf,check_mk_default
  register                        0
  check_command                   check-mk
  active_checks_enabled           1
}

define service {
  use                           check_mk_active
  host_name                     ant.demo.bitmask.i
  max_check_attempts            4
  service_description           Check_MK
}

(from redmine: created on 2014-12-11, closed on 2014-12-11, relates #6537 (closed))