handle both clientIp and clientIP in azure app gateway

[dmathieu]

What does this PR do?

There appears to be cases where Azure Application Gateway provides the client IP as json.properties.clientIP, and others where it provides it as json.properties.clientIp.

We currently only handle the former to rename the field into source.ip.

integrations/packages/azure/data_stream/application_gateway/elasticsearch/ingest_pipeline/default.yml

Lines 56 to 59 in 6e13a10

	- rename:
	field: json.properties.clientIP
	target_field: source.address
	ignore_missing: true

This change ensures a clientIp is first renamed to clientIP, so it can then become source.ip.

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

This is unit tested.

Related issues

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-09-27T13:24:19.898+0000

• Duration: 14 min 49 sec

Test stats 🧪

Test	Results
Failed	0
Passed	83
Skipped	0
Total	83

🤖 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% (10/10)	💚
Files	86.364% (19/22)	👎 -13.636
Classes	86.364% (19/22)	👎 -13.636
Methods	83.333% (155/186)	👍 3.442
Lines	85.021% (2821/3318)	👎 -12.469
Conditionals	100.0% (0/0)	💚

[zmoog]

LGTM!

We only need to bump the version and add a changelog, and we're ready to go!

[elasticmachine]

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