Fix: Adjust the process of configuring qdevice (bsc#1261884)

[liangxin1300]

This PR is to fix the problems mentioned in: #2112

• Case 1: Say qdevice is already running when rerunning the qdevice stage in the same cluster

# crm cluster init qdevice --qnetd-hostname server1 -y
INFO: Qdevice is already running on this cluster - will not reconfigure
INFO: Done (log saved to /var/log/crmsh/crmsh.log on sle16-1)

• Case 2: The maintenance mode check happens before prompting for qdevice parameters

# crm cluster init qdevice
WARNING: Please stop all running resources and try again
WARNING: Or use 'crm -F/--force' option to leverage maintenance mode
WARNING: Understand risks that running RA has no cluster protection while the cluster is in maintenance mode and restarting
INFO: Aborting the configuration change attempt
INFO: Done (log saved to /var/log/crmsh/crmsh.log on sle16-1)

• Case 3: Don't allow to replace/update qnetd server while the qdevice is running
  Will exit with the same info in case 1.
  The user must remove qdevice then re-added

[codecov]

Codecov Report

❌ Patch coverage is 83.33333% with 4 lines in your changes missing coverage. Please review.
✅ Project coverage is 70.34%. Comparing base (e4dd350) to head (5ff9a7b).
⚠️ Report is 33 commits behind head on master.

Files with missing lines	Patch %	Lines
crmsh/bootstrap.py	71.42%	4 Missing ⚠️

Additional details and impacted files

Flag	Coverage Δ
integration	55.32% <83.33%> (+<0.01%)	⬆️
unit	52.27% <70.83%> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
crmsh/constants.py	100.00% <ø> (ø)
crmsh/qdevice.py	97.15% <100.00%> (+0.03%)	⬆️
crmsh/bootstrap.py	87.49% <71.42%> (-0.21%)	⬇️

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.