modified cmd.Use for kubectl-workspaces

[apoorvajagtap]

Summary:

As sub-commands like create/create-context required additional details about workspace, whereas rest of the commands did not. So, the usage section workspace [create|create-context|<workspace>|..|.|-|~|<root:absolute:workspace>] [flags] might lead to a confusion as some sub-commands aren't specified. Modified the usage section as below, using the generic keywords:
Usage: workspace [command] [flags] workspace [command]
Considered keeping (workspace [command]) for commands like use.
Let me know, if we should only keep workspace [command] [flags] instead of both the statements.

Fixes #1579

[openshift-ci]

Hi @apoorvajagtap. Thanks for your PR.

I'm waiting for a kcp-dev member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[sttts]

not everything is a subcommand. So I don't think shortening the help text is the right direction.

[apoorvajagtap]

Hi @sttts, thanks for the inputs. I've now added use & current as well to the Usage section. Let me know if this fits better or not. Thanks again!

[sttts]

/lgtm
/approve
/ok-to-test

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sttts

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• pkg/cliplugins/OWNERS [sttts]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment