Description of problem:
"Configuration" tab should be available for an organization only in case Provisioning entitlements are provided.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create new Organization "test_org".
2. Login to "test_org".
Notice that "Configuration" tab is not available.
3. Set 1 Provisioning entitlement to "test_org".
4. Notice that "Configuration" tab is now available.
5. Set Provisioning entitlement count again back to 0 for "test_org".
"Configuration" tab is available.
"Configuration" tab is not available when Provisioning entitlements equals 0.
The problem with removing access to the Config tab when an org loses Provisioning, is that it doesn't just remove the ability to do provisioning-things to their systems - it keeps them from accessing the config-files they've set up. This is Rude.
Generally, once an org has had access to any of the 'unlockable' functionality, we don't remove it even if they lose the entitlement. Individual systems will no longer be able to BE provisioned, because that's controlled by "do they have the Provisioning entitlement assigned" - but the customer data the user has stored in Satellite should remain available.