IPinfo: Modified zip files to resolve dependency issues

[rohan-sacumen]

PR Summary

This PR resolves dependency issues in the Azure Function zip packages for all IPinfo connectors.

What’s included in this PR:
Change(s):

• Modified the zip packages for all connectors to resolve dependency issues
• Rebuilt .python_packages to ensure compatibility with the Azure Functions Linux runtime

Reason for Change(s):

• See guidance below

Version Updated:

• 3.0.5

Testing Completed:

• Tested log ingestion to Log Analytics Workspace table.
• Verified end-to-end log ingestion, data ingestion has been tested and confirmed working.

Guidance <- remove section before submitting

---

Before submitting this PR please ensure that you have read the following sections and filled out the changes, reason for change and testing complete sections:

Thank you for your contribution to the Microsoft Sentinel Github repo.

Details of the code changes in your submitted PR. Providing descriptions for pull requests ensures there is context to changes being made and greatly enhances the code review process. Providing associated Issues that this resolves also easily connects the reason.

Change(s):

• Updated syntax for XYZ.yaml

Reason for Change(s):

• New schema used for XYZ.yaml
• Resolves ISSUE Add Logstash required version to Readme file #1234

Version updated:

• Yes
• Detections/Analytic Rule templates are required to have the version updated

The code should have been tested in a Microsoft Sentinel environment that does not have any custom parsers, functions or tables, so that you validate no incorrect syntax and execution functions properly. If your submission requires a custom parser or function, it must be submitted with the PR.

Testing Completed:

• Yes/No/Need Help

Note: If updating a detection, you must update the version field.

Before the submission has been made, please look at running the KQL and Yaml Validation Checks locally.
https://github.com/Azure/Azure-Sentinel#run-kql-validation-locally

Checked that the validations are passing and have addressed any issues that are present:

• Yes/No/Need Help

Note: Let us know if you have tried fixing the validation error and need help.

References:

• Guidance for Detection checks
• General contribution guidance
• PR validation troubleshooting

---

[rohan-sacumen]

This PR is a follow-up to the previous PR #13824

[rohan-sacumen]

Hi @v-shukore,

Could you please approve the workflow run? The PR is ready for review. Thanks!

[rohan-sacumen]

Hi @v-shukore and @v-atulyadav,

All the checks have been passed. Could you please review and merge the PR at your earliest convenience today?

Thanks!

[rohan-sacumen]

Hi @v-shukore and @v-atulyadav,

Just following up on this PR. All checks have been passed. Could you please merge the PR today when you get a chance?

Thanks!

[rohan-sacumen]

Hi @v-atulyadav,

Just following up - the PR has been approved by @v-shukore. Could you please review and merge the PR today when you get a chance?

Thanks!