crmsh-4.6: Warning for `ms clone` should be non-interactive to support automation

[zzhou1]

Here is the symptom:

Exercise-1,

adm@15sp7-1:~> sudo crm configure primitive s-10 Stateful                                                                                                                      
adm@15sp7-1:~> sudo crm configure ms ms-10 s-10
WARNING: "ms" is deprecated. Please use "clone ms-10 s-10 meta promotable=true" 
warning: Support for <master> (such as in ms-30) is deprecated and will be removed in a future release. Use <clone> with a promotable meta-attribute instead.

Warnings found during check: config not valid

Do you still want to commit  (y/n)? y

adm@15sp7-1:~> sudo crm_verify --live-check -V
warning: Support for <master> (such as in ms-10) is deprecated and will be removed in a future release. Use <clone> with a promotable meta-attribute instead.
Warnings found during check: config not valid
adm@15sp7-1:~> echo $?
78

[zzhou1]

Exercise-2, crm --force can be the workaround in the automation scripts, for example,

adm@15sp7-1:~> sudo crm --force configure primitive p-10 Dummy
warning: Support for <master> (such as in ms-10) is deprecated and will be removed in a future release. Use <clone> with a promotable meta-attribute instead.
Warnings found during check: config not valid
INFO: commit forced

Exercise-3, Be cautious. Don't add --force everywhere, as it can create an incorrect configuration. For example,

adm@15sp7-1:~> sudo crm --force configure primitive p-20 Dummy-RA-Not-Exist-At-All
ERROR: ocf:heartbeat:Dummy-RA-Not-Exist-At-All: got no meta-data, does this RA exist?
warning: Support for <master> (such as in ms-30) is deprecated and will be removed in a future release. Use <clone> with a promotable meta-attribute instead.
Warnings found during check: config not valid
ERROR: ocf:heartbeat:Dummy-RA-Not-Exist-At-All: got no meta-data, does this RA exist?
ERROR: ocf:heartbeat:Dummy-RA-Not-Exist-At-All: got no meta-data, does this RA exist?
ERROR: ocf:heartbeat:Dummy-RA-Not-Exist-At-All: no such resource agent
INFO: commit forced

[zzhou1]

The root cause of the issue is that the crm_verify command uses the same return code (78, CRM_EX_CONFIG) for both warnings and errors, forcing applications like crmsh to parse the
command's text output to differentiate between them [1].

Therefore, crmsh can adapt to this crm_verify behavior when committing CIB changes, which avoids the need for an interactive user prompt for warnings.

[1] ClusterLabs/pacemaker#3933