migrate all openshift legacy commands to catalog

[Shubhamag12]

This PR migrates all openshift cmd to use catalog apis same as podman.

1. Legacy code is hidden behind --legacy flag.
2. Info is split into podman and openshift runtime and based on legacy flag here: migrate info cmd to use catalog api #1256
3. Rest of commands have common functionality, so the split is not required in that case

[adarshagrawal38]

Hey @Shubhamag12 shall we allow shorthand notation for runtime flag input
Please update the line

Suggestion:

ApplicationCmd.PersistentFlags().StringVar(&runtimeType, "runtime", "r", "", fmt.Sprintf("runtime to use (options: %s, %s) (required)", types.RuntimeTypePodman, types.RuntimeTypeOpenShift))

[Shubhamag12]

Hey @Shubhamag12 shall we allow shorthand notation for runtime flag input Please update the line

Suggestion:

ApplicationCmd.PersistentFlags().StringVar(&runtimeType, "runtime", "r", "", fmt.Sprintf("runtime to use (options: %s, %s) (required)", types.RuntimeTypePodman, types.RuntimeTypeOpenShift))

we can do that, that will require doc changes as well.
Thoughts? @yussufsh @mayuka-c

[yussufsh]

Hey @Shubhamag12 shall we allow shorthand notation for runtime flag input Please update the line
Suggestion:

ApplicationCmd.PersistentFlags().StringVar(&runtimeType, "runtime", "r", "", fmt.Sprintf("runtime to use (options: %s, %s) (required)", types.RuntimeTypePodman, types.RuntimeTypeOpenShift))

we can do that, that will require doc changes as well. Thoughts? @yussufsh @mayuka-c

We can do that, yes. No need to change docs during deployment or something; let it be explicit in the docs. Help messages are picked up anyway to depict the shorthand.

[yussufsh]

lgtm