[Heartbeat] Fix enabled flag usage in case of streams

[shahzad31]

Fixes usage of Enabled incase of data streams !!

Fix #33270

Example to test

- id: >-
    synthetics/browser-synthetics-e1a84561-a0df-49a1-b61f-0c09e0e4f25f-elastic-agent-managed-ep-default
  name: My first monitor-Test private location-default
  revision: 3
  type: synthetics/browser
  use_output: default
  meta:
    package:
      name: synthetics
      version: 0.11.0
  data_stream:
    namespace: default
  package_policy_id: e1a84561-a0df-49a1-b61f-0c09e0e4f25f-elastic-agent-managed-ep-default
  streams:
    - id: >-
        synthetics/browser-browser.screenshot-e1a84561-a0df-49a1-b61f-0c09e0e4f25f-elastic-agent-managed-ep-default
      data_stream:
        dataset: browser.screenshot
        type: synthetics
      processors:
        - add_observer_metadata:
            geo:
              name: Fleet managed
        - add_fields:
            fields:
              monitor.fleet_managed: true
            target: ''
    - id: e1a84561-a0df-49a1-b61f-0c09e0e4f25f
      name: My first monitor
      type: browser
      enabled: false
      data_stream:
        dataset: browser
        type: synthetics
      schedule: '@every 1m'
      throttling: 5d/3u/20l
      source.inline.script: |-
        step('Go to https://www.google.com', async () => {
          await page.goto('https://www.google.com');
        });
      origin: ui
      __ui:
        script_source:
          file_name: ''
          is_generated_script: false
        is_tls_enabled: true
        is_zip_url_tls_enabled: false
      processors:
        - add_observer_metadata:
            geo:
              name: Test private location
        - add_fields:
            fields:
              config_id: e1a84561-a0df-49a1-b61f-0c09e0e4f25f
              monitor.fleet_managed: true
            target: ''
      timeout: null
      screenshots: 'on'
    - id: >-
        synthetics/browser-browser.network-e1a84561-a0df-49a1-b61f-0c09e0e4f25f-elastic-agent-managed-ep-default
      data_stream:
        dataset: browser.network
        type: synthetics
      processors:
        - add_observer_metadata:
            geo:
              name: Fleet managed
        - add_fields:
            fields:
              monitor.fleet_managed: true
            target: ''

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @shahzad31? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

[elasticmachine]

Pinging @elastic/uptime (Team:Uptime)

[botelastic]

This pull request doesn't have a Team:<team> label.

[elasticmachine]

💚 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: 2022-10-10T19:06:39.122+0000

• Duration: 46 min 32 sec

Test stats 🧪

Test	Results
Failed	0
Passed	1857
Skipped	25
Total	1882

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[andrewvc]

Looks good, but needs a unit test. Can you add it? If not, I can submit one, just let me know

[andrewvc]

LGTM now that there's a unit test and Changelog