add playbook links to documentation section for playbook alert (#594)

alerts/google-gke/failedscheduling-log-event-within-cluster.v1.json

@@ -2,7 +2,7 @@
  "displayName": "GKE Pod - FailedScheduling Log Event (${CLUSTER_NAME})",
  "documentation": {
  "content":
- "- A \"FailedScheduling\" event occurs when a pending pod cannot be scheduled, This alert fires when an event with reason \"FailedSceduling\" occurs in the logs; limited to notifying once per hour.",
+ "- A \"FailedScheduling\" event occurs when a pending pod cannot be scheduled, This alert fires when an event with reason \"FailedSceduling\" occurs in the logs; limited to notifying once per hour.\n- We recommend troubleshooting this issue with the [Unschedulable Pods Interactive Playbook](https://console.cloud.google.com/monitoring/dashboards/gke-troubleshooting/unschedulable?project=${PROJECT_ID}&f.sd_ts_playbook.cluster_name=${CLUSTER_NAME}&f.sd_ts_playbook.location=${CLUSTER_LOCATION}) which shows detailed instructions, metrics, and logs.",
  "mimeType": "text/markdown"
  },
  "userLabels": {},

alerts/google-gke/restarts-containers-within-cluster.v1.json

@@ -1,7 +1,7 @@
 {
  "displayName": "GKE Container - Restarts (${CLUSTER_NAME} cluster)",
  "documentation": {
- "content": "- Container restarts are commonly caused by memory/cpu usage issues and application failures.\n- By default, this alert notifies an incident when there is more than 1 container restart in a 5 minute window. If alerts tend to be false positive or noisy, consider visiting the alert policy page and changing the threshold, the rolling (alignment) window, and the retest (duration) window. [View Documentation](https://cloud.google.com/monitoring/alerts/concepts-indepth).",
+ "content": "- Container restarts are commonly caused by memory/cpu usage issues and application failures.\n- By default, this alert notifies an incident when there is more than 1 container restart in a 5 minute window. If alerts tend to be false positive or noisy, consider visiting the alert policy page and changing the threshold, the rolling (alignment) window, and the retest (duration) window. [View Documentation](https://cloud.google.com/monitoring/alerts/concepts-indepth).\n- We recommend troubleshooting this issue with the [Interactive Playbook](https://console.cloud.google.com/monitoring/dashboards/gke-troubleshooting/crashloop?project=${PROJECT_ID}&f.sd_ts_playbook.cluster_name=${CLUSTER_NAME}&f.sd_ts_playbook.location=${CLUSTER_LOCATION}) for restarting containers which shows detailed instructions, metrics, and logs.",
  "mimeType": "text/markdown"
  },
  "userLabels": {},