Contentctl

This resolves a bug which causes all contentctl operations to fail with Pydantic >= 2.10

What's Changed
* Pin Pydantic to Resolve Contentctl Bug by pyth0n1c in https://github.com/splunk/contentctl/pull/332


**Full Changelog**: https://github.com/splunk/contentctl/compare/v4.4.6...v4.4.7

contentctl does not yet support Python 3.13. This was not reflected in the pyproject.toml and thus Pypi.
This release updates the compatibility here and on Pypi. At this time, contentctl supports Python 3.11 and 3.12.

Look for Python 3.13 support in an upcoming release!

What's Changed
* don't declare py3.13 compat by ljstella in https://github.com/splunk/contentctl/pull/329


**Full Changelog**: https://github.com/splunk/contentctl/compare/v4.4.5...v4.4.6

Ensure that when testing using `mode:changes`, updates to an underlying data_source object used by a detection mean that the detections which reference it must be retested.

What's Changed
* Ensure we print the right field for data_source by ljstella in https://github.com/splunk/contentctl/pull/324
* Testing on Datasource changes by ljstella in https://github.com/splunk/contentctl/pull/301


**Full Changelog**: https://github.com/splunk/contentctl/compare/v4.4.4...v4.4.5

This addresses a number of appinspect warnings and enables deploying via appinspect.


What's Changed
* Enable acs deploy + appinspect warnings by pyth0n1c in https://github.com/splunk/contentctl/pull/146


**Full Changelog**: https://github.com/splunk/contentctl/compare/v4.4.3...v4.4.4

This fixes a serious problem that caused all integration testing to fail due to an incorrect path used for scheduling a savedsearch.
There may still be some testing issues with this release, but this is definitely more correct than previously.

This supercedes 4.4.2 which had a bug where the version was not updated in pyproject.toml, meaning that the upload to Pypi failed.

What's Changed
* Fix savedsearches path issue by pyth0n1c in https://github.com/splunk/contentctl/pull/316
* remove "cloud" from the security_domain enum by pyth0n1c in https://github.com/splunk/contentctl/pull/314


**Full Changelog**: https://github.com/splunk/contentctl/compare/v4.4.1...v4.4.3

Update CLI release_notes workflow for a bit more control on the branch we diff against to generate those notes. Previously, we could only diff against a tag.

What's Changed
* add --compare_against flag to release_notes action by patel-bhavin in https://github.com/splunk/contentctl/pull/311


**Full Changelog**: https://github.com/splunk/contentctl/compare/v4.4.0...v4.4.1