CLI-980 Refactor confluent iam acl parameter names to match those of underlying API

[MuweiHe]

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

Rename list fields in confluent iam acl commands from {"KafkaClusterId", "Principal", "Permission", "Operation", "Host", "Resource", "Name", "Type"} to {"KafkaClusterId", "Principal", "Permission", "Operation", "Host", "ResourceType", "ResourceName", "PatternType"}

References

Test&Review

[brianstrauch]

This is an issue that existed before this PR (see KafkaClusterId), but we're using upper camel case for the "human" output... do we really want to be doing this?

[DABH]

This is an issue that existed before this PR (see KafkaClusterId), but we're using upper camel case for the "human" output... do we really want to be doing this?

@brianstrauch What are our other options? KafkaClusterID? Wonder what is best practice / pros and cons? Could check with Ethan?

[DABH]

This seems right afaict

[brianstrauch]

@brianstrauch What are our other options? KafkaClusterID? Wonder what is best practice / pros and cons? Could check with Ethan?

@DABH @MuweiHe A ListOutputWriter takes three slices of strings, the second of which is called humanLabels, which in this case should look like the following (should look like titles instead of using UpperCamelCase) because they're used for the titles of the tables:

var humanFields = []string{"Kafka Cluster ID", "Principal", "Permission", "Operation", "Host", "Resource Type", "Resource Name", "Pattern Type"}

It looks like the regular fields variable is being used for the listLabels and humanLabels

cli/internal/cmd/iam/command_acl.go

Line 234 in 40eaaf2

outputWriter, err := output.NewListOutputWriter(cmd, fields, fields, structuredRenames)