Ensure new version of `cac` is released when acp-client-go is updated

[timsearle]

cac is tightly coupled to the specifications inside acp-client-go as it relies on those clients to make API calls. However, those specs can be updated and cac falls out of sync.

This makes cac unreliable when configuration changes are made, e.g.:

validation failure list:
pools.<pool_id>.second_factor_authentication_mechanisms.0 in body should be one of [password otp webauthn]

And totp is currently supported.

At a minimum - can a new version be released now? But ideally this becomes automated.

[piotrek-janus]

Hey Tim,

Thanks for opening this ticket.

I agree, it makes sense to either have a new version of CAC whenever there is a new acp-client-go version, or decouple validation.

As suggested, I've started with a manual update: #35

[piotrek-janus]

@timsearle, I've released v1.6.1 with updated acp-client-go