Description of problem:

We are planning to disable the DeploymentConfig capability by default starting OCP 4.19. Customers are therefore migrating their DeploymentConfigs to Deployments (see also OCPSTRAT-1465).

Most of the `oc rollout` commands work as expected with Deployments (apart from `oc rollout latest` and `oc rollout cancel`). However the `oc rollout --help` text still only references DeploymentConfigs while it should also reference Deployments, DaemonSets and StatefulSets, which confuses customers:

$ oc rollout --help
Start a new rollout, view its status or history, rollback to a previous revision of your app.

 This command allows you to control a deployment config. Each individual rollout is exposed as a replication controller,
and the deployment process manages scaling down old replication controllers and scaling up new ones. [..]

We should remove the references to `DeploymentConfig` in the help text and either use the `kubectl` help text or also include Deployments and StatefulSets.

Version-Release number of selected component (if applicable):

$ oc version
Client Version: 4.17.6
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: 4.17.5
Kubernetes Version: v1.30.5

How reproducible:

Always

Steps to Reproduce:
1. Run `oc rollout --help`

Actual results:

The help text describes that these commands are for controlling DeploymentConfigs.

Expected results:

The help text describes that these commands are for controlling Deployments, StatefulSets, DaemonSets and also DeploymentConfigs.

Additional info:

Potentially we should also look into enabling `oc rollout cancel` for Deployments. For `oc rollout latest` there is no equivalent in Deployments, so not having support for this one should be fine.

CC rh-ee-kniederw