Disabling Push Gateway should not require register server & accept privacy terms

Description:

Disabling Push Gateway should not require register server & accept privacy terms

Steps to reproduce:

1. Install Rocket.Chat and do not register server
2. Go to Administration > Push

Second issue:

1. Even after register server & accept privacy terms

2. Set Enable Gateway to unchecked

   

3. Click Save changes -> sometimes "Enable gateway" is immediately checked again

4. Refresh browser

5. Rocket.Chat displays "Cloud registration is still pending" then "Enable gateway" is checked again.

Expected behavior:

Disabling Gateway should be possible, which will enable GCM Keys etc. to be set.

Actual behavior:

Gateway is "checked" but can't be disabled. GCM Keys etc. cannot be set.

Second issue:

Rocket.Chat displays "Cloud registration is still pending" then "Enable gateway" is checked again.

Cloud registration is still pending
Mobile notifications will not work until the registration is finished. Learn more

Server Setup Information:

• Version of Rocket.Chat Server: 3.6.1
• Operating System: Docker
• Deployment Method: Docker or AWS Fargate
• Number of Running Instances: 1
• DB Replicaset Oplog: local
• NodeJS Version: 12
• MongoDB Version: 4.0

Client Setup Information

• Desktop App or Browser Version: Chrome
• Operating System: Ubuntu 20.04.1

Additional context

MongoDB collection rocketchat_settings seems to confirm the value is already false, but for some reason Admin UI insists it's checked.

Relevant logs:

Start at Administration > Push and reproduce the behavior with an unregistered server, then after registration with Enable Gateway unchecked. Trace the setting and cloud-registration state from the admin UI through save and refresh; done means the gateway can remain disabled and GCM keys can be configured without requiring registration or privacy-term acceptance.