CLI-997: removes all usages of user.organization_id throught the CLI

[zzbennett]

Checklist

1. [CRUCIAL] Is the change for CP or CCloud functionalities that are already live in prod?

   • yes: ok

2. Did you add/update any commands that accept secrets as args/flags?

   • no: ok

What

We are deprecating user.organization_id in favor of organization.id, which should always be fetched from the auth context or explicitly passed in via parameters. This is for project nexus's initiative to support multiple users per org--we can no longer assume a user belongs to only one org, therefore we cannot rely on the user.organization_id field anymore.

References

Test&Review

I built this locally with a version of cc-structs that does not have user.organization_id defined and found all the places where that field is referenced and replaced them with organization.id, or removed the user.organization_id entirely, since in almost all our APIs the organization id is read from the jwt token and not from explicitly api parameters.

gonna wait for the ci jobs to pass, since this does not introduce any new logic, we just want to avoid regressions

[ziru]

lgtm

[mtodzo]

lgtm when CI passes

[mtodzo]

Is this intentional? Looks like this might be reason for the test failure

[zzbennett]

oh yes, it is to pull in my dependent ccloud-sdk-go PR here https://github.com/confluentinc/ccloud-sdk-go-v1/pull/147 I wanted to run the ccloud-sdk-go changes through the CLI CI jobs before merging it. I will update the version here though before merging the CLI PR.

[mtodzo]

@DABH Is a golreleaser bump ok? Idk i can't remember if this has caused issues in the past

[DABH]

In general we should probably just keep it the same if possible. It takes a few extra changes to really upgrade the version...

[zzbennett]

ah did not mean to bump that up. I did run go get goreleaser which must have bumped the version