Removing detection rules from the ded package

[ajosh0504]

What does this PR do?

This PR moves detection rules associated with Data Exfiltration Detection (ded) out of the integration package.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.

How to test this PR locally

• Spin up a local Elasticsearch cluster
• Verify that the package version shown is 2.0.0, Subscription is platinum and License is Elastic-2.0
• Install the Data Exfiltration Detection assets
• Verify that no detection rules with the Data Exfiltration tag show up on the Rules Management page under Security
• Verify that the job IDs have been updated when you click on the Data Exfiltration card under Anomaly Explorer

Related Issues

Not linking since these are internal issues

Screenshots

• Version shows 2.0 while installing assets

• No rules appear upon installing assets

• Job IDs have been updated

[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: 2023-10-05T21:25:14.595+0000

• Duration: 14 min 23 sec

Test stats 🧪

Test	Results
Failed	0
Passed	1
Skipped	0
Total	1

🤖 GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

[peteharverson]

Changes to ML job and datafeed IDs LGTM.

[sodhikirti07]

Changes LGTM!

[elasticmachine]

Package ded - 2.0.0 containing this change is available at https://epr.elastic.co/search?package=ded