{microsoft_defender_endpoint, m365_defender}.vulnerability: New API implementationExisting CEL program uses 3 API endpoints to fetch vulnerabilitydata. Although we fetch more fields using this approach, it doesn't scale well and hence is unusable even for few hundred machines.This PR updates the vulnerability data stream with new SoftwareVulnerabilitiesExport API[1], which is recommended for larger workloads. While there are few data points missed in this new implementation[2], we maintain all the required fields for 3rd party vulnerability workflow[3].Other changes:- Updates microsoft_defender_endpoint min stack version to "8.19.3"  as the permissions for the transform were actually applied in   "8.19.3" version, and not in "8.19.2"[4].- Add dataset filter to all visualisations of vulnerability dashboards.[1]: https://learn.microsoft.com/en-us/defender-endpoint/api/get-assessment-software-vulnerabilities#2-export-software-vulnerabilities-assessment-via-files[2]: https://github.com/elastic/integrations/issues/15521#issuecomment-3380969284[3]: https://docs.elastic.dev/security-solution/cloud-security/cdr/3p-dev-guide[4]: https://github.com/elastic/elasticsearch/pull/132629

--- Test results for package: m365_defender - START ---╭───────────────┬───────────────┬───────────┬───────────────────────────────────────────────────┬────────┬──────────────╮│ PACKAGE       │ DATA STREAM   │ TEST TYPE │ TEST NAME                                         │ RESULT │ TIME ELAPSED │├───────────────┼───────────────┼───────────┼───────────────────────────────────────────────────┼────────┼──────────────┤│ m365_defender │ vulnerability │ pipeline  │ (ingest pipeline warnings test-vulnerability.log) │ PASS   │ 480.561041ms ││ m365_defender │ vulnerability │ pipeline  │ test-vulnerability.log                            │ PASS   │  87.309125ms │╰───────────────┴───────────────┴───────────┴───────────────────────────────────────────────────┴────────┴──────────────╯--- Test results for package: m365_defender - END   ---Done