Bug 1542325

Description of problem:
oc status should not suggest "oc set probe pod" because pod updates may not change fields other than a few fields `spec.containers[*].image`, `spec.initContainers[*].image`, `spec.activeDeadlineSeconds` etc. (See below output for more).

Version-Release number of selected component (if applicable):
v3.9.0-0.38.0

How reproducible:
Always

Steps to Reproduce:
1. oc new-app -f https://raw.githubusercontent.com/openshift/origin/master/examples/sample-app/application-template-stibuild.json
2. oc status -v
3. Per the output suggestion, run `oc set probe pod/database-1-deploy --liveness -- echo ok`
4. Check `oc set probe -h`

Actual results:
2. Shows:
...
Info:
  * pod/database-1-deploy has no liveness probe to verify pods are still running.
    try: oc set probe pod/database-1-deploy --liveness ...
  * pod/database-1-hook-mid has no liveness probe to verify pods are still running.
    try: oc set probe pod/database-1-hook-mid --liveness ...
  * pod/database-1-hook-pre has no liveness probe to verify pods are still running.
    try: oc set probe pod/database-1-hook-pre --liveness ...
  * pod/ruby-sample-build-1-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/ruby-sample-build-1-build --liveness ...
  * dc/database has no readiness probe to verify pods are ready to accept traffic or ensure deployment is successful.
    try: oc set probe dc/database --readiness ...
  * dc/database has no liveness probe to verify pods are still running.
    try: oc set probe dc/database --liveness ...
  * dc/frontend has no readiness probe to verify pods are ready to accept traffic or ensure deployment is successful.
    try: oc set probe dc/frontend --readiness ...
  * dc/frontend has no liveness probe to verify pods are still running.
    try: oc set probe dc/frontend --liveness ...
...


3. It fails with message, which is a bit messy and field names in the output are initially upper case.
error: Pod "database-1-deploy" is invalid: spec: Forbidden: pod updates may not change fields other than `spec.containers[*].image`, `spec.initContainers[*].image`, `spec.activeDeadlineSeconds` or `spec.tolerations` (only additions to existing tolerations)
{"Volumes":[{"Name":"...<snipped big paragraph>..."LivenessProbe":
A: {"Exec":{"Command":["echo","ok"]},...<snipped big paragraph>...
B: null,"ReadinessProbe":null...<snipped big paragraph>...

4. It shows: Set or remove a liveness or readiness probe from a pod or pod template

Expected results:
2. Should not show "oc set probe pod" because pod fields (except some, e.g. spec.containers[*].image etc) cannot be changed.
3. `oc set probe pod` message is better to be concise and field names in the output are initially lower case.
4. It should not say it can be used for "a pod", like `oc set env/volumes -h` only mention pod template and don't mention pod.

Additional info:
This bug includes `oc status -v` output, `oc set probe pod` output, `oc set probe -h` output. If separate bugs are needed respectively for them, feel free to tell me to file separate ones