added GetSensorUsageHourly as this allows you to pull hourly billing based on Cloud calculated billing.

[atav928]

Added GetSensorUsageHourly to _sensor_usage.py endpoint; tested it in production, and works by providing either hourly or weekly billing usage depending on how billing is calculated. This is part of CrowdStrike documentation and also shows in the billing dashboard how these values are pulled. This helps calculate the Cloud (reserved hourly) usage. The endpoint that is not documented, but works along with getting weekly billing information is: "/billing-dashboards-usage/aggregates/hourly-average/v1"

Please review our Code of Conduct
and our Contribution Guidelines before submitting a Pull Request.

REMOVE ALL PULL REQUEST HINTS BEFORE SUBMITTING

PULL REQUEST TITLE

Pull Request general description should go here.

Please fill out all values and then remove any help text before submitting your PR.
Refer to this PR as a reference example!

• Enhancement
• Major Feature update
• Bug fixes
• Breaking Change
• Updated unit tests
• Documentation
• Code sample

Check the values above that match your PR and remove the remaining.

Unit test coverage

pytest tests/test_sensor_usage.py -v
============================================================ test session starts ============================================================
cachedir: .pytest_cache
rootdir: /GitHub/falconpy
configfile: pyproject.toml
plugins: cov-6.3.0
collected 1 item                                                                                                                            

tests/test_sensor_usage.py::TestSensorUsage::test_all_code_paths PASSED                                                               [100%]

============================================================= 1 passed in 1.97s =============================================================

Bandit analysis

BANDIT ANALYSIS RESULTS SHOULD BE POSTED
HERE. PLEASE REVIEW CONTRIBUTING.md FOR
MORE DETAILS ON GENERATING BANDIT RESULTS

Added features and functionality

• If your PR adds features or functionality, what should be included in the next release notes?
  Added support for pulling hourly billing data from billing-dashboard-usage endpoint on top of the weekly-average values.

Issues resolved

• Bug fix: Please list related bugs individually. Identifying the ticket or bug report in the PR description auto-updates the affected ticket and helps the community with ticket triage. For example:

• Fixes feat: add gov2 container upload url #1234 by doing foo
• Mitigates https://github.com/CrowdStrike/falconpy/issues/5678 by updating bar.

• BE EXPLICIT in what you are resolving

Other

• List any other details here
• Documentation regarding your changes can also be listed here