[BUG] Backup tab is shown when Backup Framework is not enabled

[PaulAngus]

Describe the bug

A 'Backup' tab is shown under storage when the Backup Framework has not been enabled. This will cause many 'support calls' when users want try to create backups.

To Reproduce
Steps to reproduce the behavior:

1. Ensure backup framework is not enabled
2. Click on 'Storage' tab
3. See error

Expected behavior

The backup tab should not be visible as the backup framework is not enabled.

Screenshots

Desktop (please complete the following information):

• OS: [e.g. Windows, Mac, iOS, Android with device/screen details if applicable]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

[yadvr]

With @davidjumani

• Remove the view backup and vmsnapshot button via config::related for compute.js
• Instead add tabs to the VM instance/detail component to show/hide both backup and vm snapshots (similar to the volumes, nics etc tabs) depending on user-role access and availability of feature

@PaulAngus Lowering severity to Critical, we'll fix the issue for 1.0/GA but let's use blocker limited to issues where a feature is broken (i.e. does not work, than a visibility/usabilty issue)

[PaulAngus]

A release blocker is an issue that must be fixed prior to a release. therefore blocker is the correct category.

Requiring the operator to hide the feature is not acceptable. the kubernetes plugin tab is only visible when the kubernetes plugin is enabled. The same should be true for the backup plugin. The operator should not have to fix inadequacies in ACS code.

[yadvr]

@PaulAngus I've already said show/hide "depending on user-role access" and "availability of feature" so why is that unacceptable? Why is this a release blocker?

[yadvr]

Legacy UI also show the backups view and offering even when the feature is disabled globally and for all zones

Using http://docs.cloudstack.apache.org/en/latest/adminguide/backup_and_recovery.html as a reference, if the feature is not globally enabled (backup.framework.enabled) then it must not be considered enabled; therefore the feature is considered enabled for a zone when it's globally enabled and enabled for a zone apache/cloudstack#4202
This will fix exporting the APIs, if feature is disabled it won't export APIs and clients such as cmk, Primate won't show APIs or views.

[yadvr]

With @davidjumani

[PaulAngus]

Viewed PR on-screen with DJ - fix LGTM