fix: handle boolean strings from Splunk Cloud API for HEC useACK field

[pgiraultmatz]

Problem

On Splunk Cloud deployments, terraform apply fails with:

json: invalid use of ,string struct tag, trying to unmarshal "false" into int

This happens because Splunk Cloud returns "useACK": "false" in HEC token API responses, while the HttpEventCollectorObject struct declares UseACK as int with a json:",string" tag — which only handles integer strings like "0" or "1".

Splunk Enterprise returns "0"/"1", Splunk Cloud returns "false"/"true". The existing struct tag cannot handle both.

Fix

Introduce SplunkBoolInt, a custom int type with a UnmarshalJSON that accepts:

• Boolean strings: "true" → 1, "false" → 0 (Splunk Cloud)
• Integer strings: "1" → 1, "0" → 0 (Splunk Enterprise)
• Raw integers: 1 → 1, 0 → 0

MarshalJSON serializes back as an integer string ("0"/"1") to preserve compatibility with the Splunk API write path.

Files changed

• client/models/splunk_bool_int.go — new SplunkBoolInt type
• client/models/splunk_bool_int_test.go — unit tests covering all cases including the Splunk Cloud regression
• client/models/http_event_collector.go — UseACK field changed from int to SplunkBoolInt
• splunk/resource_splunk_inputs_http_event_collector.go — cast updated accordingly

Testing

go test ./client/models/... -v

All tests pass. The TestHttpEventCollectorObject_UnmarshalUseACK test directly reproduces the Splunk Cloud API response that triggered the bug.

Notes

The same int json:",string" pattern exists in global_http_event_collector.go and saved_searches.go. Those fields may be affected by the same issue on Splunk Cloud — SplunkBoolInt can be reused to fix them incrementally.

[pgiraultmatz]

cc @rrossetti-splunk @micahkemp-splunk — would appreciate a review when you get a chance. This fixes a crash on Splunk Cloud deployments where the API returns boolean strings for useACK instead of integer strings.