Pre-built ML jobs for uptime are not expected to be proposed for Synthetics

[herrBez]

Kibana version: 8.13.2

Elasticsearch version: 8.13.2

Server OS version: N/A Elastic Cloud

Browser version: Google Chrome 124.0.6367.61 (Official Build) (64-bit)

Browser OS version: Windows 11

Original install method (e.g. download page, yum, from source, etc.): Elastic Cloud

Describe the bug:
When creating a ML job on Synthetics datastream, the Heartbeat (Uptime) jobs are proposed. This is due to the fact that the manifest of the uptime ML job looks for data with agent.type: "heartbeat". This behavior is not expected and the job do not work either because of #181105 .

Steps to reproduce:

1. Collect synthetics
2. Create a ML job on the synthetics dataset
3. Check that the Heartbeat job is proposed

Expected behavior:
The uptime jobs should not be proposed for Heartbeat

Screenshots (if relevant):
N/A

Errors in browser console (if relevant):
N/A

Provide logs and/or server output (if relevant):
N/A

Any additional context:

• Internal Slack Discussion: https://elastic.slack.com/archives/CE4MRBU48/p1712816726385989
• Related to Prebuilt ML job for Heartbeat looks for no-more-existent dataset "uptime"  #181105

[elasticmachine]

Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services)

[elasticmachine]

Pinging @elastic/obs-ux-management-team (Team:obs-ux-management)

[jasonrhodes]

Is this a duplicate of #181105 ? cc: @drewpost @paulb-elastic