cisco_umbrella: don't clobber temporary field when collecting identities

[efd6]

Proposed commit message

Previously, the cisco.umbrella._tmp field was unconditionally being assigned a new hash map when cisco.umbrella.identity contained multiple identities, deleting already collected information including the @timestamp. Fix this by making the map construction conditional.

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.

Author's Checklist

• [ ]

How to test this PR locally

Related issues

• Fixes Error in Pipeline used within Cisco Umbrella Integration - timestamp not mapped correctly #8517

Screenshots

[efd6]

/test

[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-11-20T01:14:34.039+0000

• Duration: 24 min 27 sec

Test stats 🧪

Test	Results
Failed	0
Passed	11
Skipped	0
Total	11

🤖 GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (1/1)	💚
Files	100.0% (1/1)	💚
Classes	100.0% (1/1)	💚
Methods	100.0% (21/21)	💚 50.0
Lines	95.027% (535/563)	👎 -4.973
Conditionals	100.0% (0/0)	💚

[elasticmachine]

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

[elasticmachine]

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