SSPROD-29308: Implement CloudAccount client v2 for Secure

[ravinadhruve10]

Change summary:

Adding a new Cloudauth Account client for making Secure BE (cloudauth) APIs to support API-only onboarding support.

[nkraemer-sysdig]

Maybe we can use a cloudauth prefix instead of a v2 suffix across the board? E.g. name the file sysdig/internal/client/v2/cloudauth.go and the constants cloudauthAccountPath/cloudauthAccountsPath?

Seems a bit odd to add v2s across the board, especially when refering to an endpoint with v1 in it

Yes, that works too and that's a fair point. I named it with v2 as per the framework suggestion, similar to how they did for alerts_v2.go. But cloudauth also works. (as long as we don't change the name of the service).

[ravinadhruve10]

Maybe we can use a cloudauth prefix instead of a v2 suffix across the board? E.g. name the file sysdig/internal/client/v2/cloudauth.go and the constants cloudauthAccountPath/cloudauthAccountsPath?

Seems a bit odd to add v2s across the board, especially when refering to an endpoint with v1 in it

Yes, that works too and that's a fair point. I named it with v2 as per the framework suggestion, similar to how they did for alerts_v2.go. But cloudauth also works. (as long as we don't change the name of the service).

Done!

[ravinadhruve10]

All the latest changes are pulled and merged as part of #407 . Closing this PR then.