Fix SecOps rule detection arguments

[abdeltaehass]

Summary

• pass ChronicleClient.list_detections filters and pagination arguments by keyword
• expose optional start_time, end_time, and list_basis parameters through get_rule_detections
• add focused regression coverage for alert-state, pagination, and time-range forwarding

Root cause

get_rule_detections passed alert_state, page_size, and page_token positionally. The Chronicle SDK places start_time, end_time, and list_basis before those parameters, so values such as "ALERTING" were bound to start_time and failed when the SDK called strftime().

The wrapper now uses explicit keyword arguments and converts optional ISO-8601 time strings to datetime objects before calling the SDK.

Fixes #263

Validation

• focused get_rule_detections tests: 2 passed
• SecOps unit tests: 18 passed
• git diff --check: passed

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[abdeltaehass]

Friendly ping on this one. CI is green and it still merges cleanly.

Happy to rebase, split it up, or add more test coverage if any of that would help. Is there anything else I can do to move it along?

[dandye]

Thank you for your contribution, @abdeltaehass! I'll try to review ASAP.

[dandye]

I know you are following precedent in this project, so there is no blame, but this has some issues, which I've described in #291. I think I will fast follow with a fix of all occurrences of this rather than block your PR.