[cisco_ise] Add Support of Timezone Configuration Parameter

[mohitjha-elastic]

Proposed Commit Message

cisco_ise: add support for timezone offset in configuration parameter of all the input types.

This adds support for the timezone offset as a configuration parameter in all the three input types to adjust
the timezone when importing logs from a host in a different timezone so that datetimes are
appropriately interpreted.

This change has been tested on the data available in the test folder.

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.

How to test this PR locally

Clone integrations repo.
Install the elastic package locally.
Start the elastic stack using the elastic package.
Move to integrations/packages/cisco_ise directory.
Run the following command to run tests.
elastic-package test -v

Related issues

It closes issue #24307 from the enhancements repo.

[elasticmachine]

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

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 375fc40

cc @mohitjha-elastic

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

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

See analysis details on SonarQube

[elasticmachine]

Pinging @elastic/sec-deployment-and-devices (Team:Security-Deployment and Devices)

[taylor-swanson]

Suggested change

	link: https://github.com/elastic/integrations/pull/1
	link: https://github.com/elastic/integrations/pull/13540

[taylor-swanson]

So this will give the configuration priority over a time zone seen in a log, is this intended behavior? In other Cisco integrations, the priority is log, then configuration.

Should we reverse the order here so the log time zone is given priority and if it isn't present, then we use the time zone from configuration?