Description of problem:
In the past AllowClusterWithVirtGlusterEnabled was explicitly set to False at setup time to prevent the users from trying an unsupported hyper-converged deployment by mistake.
Now, due to the hyperconverged effort, we have to remove that lock.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. deploy hosted-engine with rhevm-appliance
2. check the initial value of AllowClusterWithVirtGlusterEnabled with engine-config
AllowClusterWithVirtGlusterEnabled is initially False
AllowClusterWithVirtGlusterEnabled is initially True
Tested with RHV 18.104.22.168
'AllowClusterWithVirtGlusterEnabled' is set to 'true' by default
[root@ ~]# engine-config -g AllowClusterWithVirtGlusterEnabled
AllowClusterWithVirtGlusterEnabled: true version: general