ti_abusech: Fix ECS date mapping on threat fields.

[kcreddy]

Proposed commit message

Fix ECS date mapping for threat fields.

ecs@mappings component template is missing threat fields 
mapped as date. Example: fields such as first_seen, last_seen, 
modified_at are being mapped as keyword in transform's source 
datastream-backed indices. The transform's destination indices
are not effected as they are not datastream-backed and mappings
are explicitly defined as date. This causes field type conflicts.

   - Explicitly add ECS threat fields that are of type date into 
     source data-stream backed fields.

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.

Related issues

• Relates [Threat Intelligences Utilities]: Intelligence Dashboard in Elastic Security Broken #10612

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 9c69ca9

History

• 💔 Build #14099 failed 84023ae

cc @kcreddy

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
83.3% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[elasticmachine]

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

[efd6]

No change in ingest and tests since these fields are already handled there; this just ensures correct mapping.

[elasticmachine]

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