add types for status alert

[shahzad31]

add types for status alert

status alert can be enabled/disable using

    monitor.use({
      schedule: 10,
      alert: {
        status: {
          enabled: false,
        },
      },
    });

in lightweight:

heartbeat.monitors:
- type: http
  name: Todos Lightweight
  id: todos-lightweight
  enabled: true
  urls: "https://elastic.github.io/synthetics-demo/"
  schedule: '@every 3m'
  timeout: 16s
  alert.status.enabled: true

[apmmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-03-20T17:01:45.723+0000

• Duration: 14 min 43 sec

Test stats 🧪

Test	Results
Failed	0
Passed	214
Skipped	2
Total	216

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[vigneshshanmugam]

Probably this is a bit of a different usage case, Do you foresee a future where we might want to disable individual alerts for monitor instead of just disabling them all which is what the PR is doing.

So its of the type here it would be like alert: []Alerts for a given monitor. /cc @dominiqueclarke

[vigneshshanmugam]

not used.

[dominiqueclarke]

Probably this is a bit of a different usage case, Do you foresee a future where we might want to disable individual alerts for monitor instead of just disabling them all which is what the PR is doing.

So its of the type here it would be like alert: []Alerts for a given monitor. /cc @dominiqueclarke

I think we envision the type being an object representing the different alerts, rather than an array, which we can add to later. So let's say we added a tls alert, the type would be

alerts: {
   status: {
       enabled: boolean
   },
   tls: {
       enabled: boolean
   },
}

[dominiqueclarke]

LGTM but you may want to add a test.

Also, and this isn't a blocker for me, it doesn't support nested yaml for lightweight monitors, only alert.status.enabled