rpk: add rpk cluster quotas import

[r-vasquez]

This PR introduces a new command: rpk cluster quotas import

Usage:

import uses a string source that should be formatted as the output of rpk cluster quotas describe --format <json/yaml>. It accepts either the string, or a file containing the json (or yaml) representation of the import source:

$ rpk cluster quotas import --from {quotas:[...]}

$ rpk cluster quotas import --from /path/to/file

The command issues an alterQuotas request, deleting the old quotas, hence, a confirmation prompt is needed:

$ rpk cluster quotas import --from /tmp/foo.json
ENTITY                 QUOTA-TYPE          OLD-VALUE  NEW-VALUE
client-id=<default>    consumer_byte_rate  3333       -
client-id-prefix=bar-  consumer_byte_rate  32333123   23123123
? Confirm client quotas import above? Yes
Successfully imported the client quotas

Backports Required

• none - not a bug fix
• none - this is a backport
• none - issue does not exist in previous branches
• none - papercut/not impactful enough to backport
• v24.1.x
• v23.3.x
• v23.2.x

Release Notes

Features

• rpk: introduce a command to import cluster client quotas: rpk cluster quotas import.

[Deflaimun]

From a user perspective I would prefer to see what's the acceptable schema in this help text.

However I can understand from a development/design perspective that the schema can change and the source will be the command that generates it.

Considering the above, can we include the acceptable schema in this help text? If not, it's fine. I defer to you guys what's the best approach.

[Feediver1]

Left some updates for active voice/clarity.

[r-vasquez]

Force Push:

After internal discussion:

• Replace --source to --from
• Now --from accepts either a json, yaml or a file, rpk will identify which one to use and @ is not needed.
• Added the schema of the import string to the help text
• Doc changes.