[Security Solution] Add data_stream.dataset into Packetbeat ML job queries

[andrewkroh]

Describe the bug:

The network_traffic Fleet integration sets the constant_keyword data_stream.dataset field rather than event.dataset. For the jobs to work on data from Agent (and from standalone Packetbeat) they need to expand their queries. Multiple files are affected:

x-pack/platform/plugins/shared/ml/server/models/data_recognizer/modules/security_packetbeat/ml/datafeed_*.json

For example:

kibana/x-pack/platform/plugins/shared/ml/server/models/data_recognizer/modules/security_packetbeat/ml/datafeed_packetbeat_rare_user_agent.json

Lines 8 to 11 in 1882697

	"should": [
	{ "term": { "event.dataset": "http" } },
	{ "term": { "event.dataset": "network_traffic.http" } }
	],

Any additional context (logs, chat logs, magical formulas, etc.):

• [Network Packet Capture]: No more GeoIP resolution and event.dataset missing integrations#10956 (comment)
• https://discuss.elastic.co/t/wrong-ml-job-query-packetbeat-rare-user-agent-or-missing-event-dataset-in-network-traffic-data/377283

[elasticmachine]

Pinging @elastic/security-solution (Team: SecuritySolution)