infoblox_bloxone_ddi: fix handling of options fields

[efd6]

Proposed commit message

We have a report of the options field of the dhcp_lease dataset coming in as a string rather than an object, so conditionally on type, apply a JSON parse processor. There is also an options field in the dns_data datastream, so defensively also apply the change there, though note #7924 (comment).

/cc @MakoWish

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 [Infoblox BloxOne DDI] Failure to Ingest DHCP Lease Logs #7924

Screenshots

[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-04T19:57:08.835+0000

• Duration: 17 min 20 sec

Test stats 🧪

Test	Results
Failed	0
Passed	19
Skipped	0
Total	19

🤖 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% (3/3)	💚
Files	100.0% (3/3)	💚
Classes	100.0% (3/3)	💚
Methods	100.0% (42/42)	💚 12.963
Lines	98.303% (2607/2652)	👍 11.78
Conditionals	100.0% (0/0)	💚

[elasticmachine]

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

[elasticmachine]

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