Add checks for Subscription dependencies so they cannot be updated inconsistently

[GAlexIHU]

Overview

• Disallow updating custom UsageAttribution if a Subscription is present
• Disallow archiving features used in active or scheduled plans or subscriptions

Notes for reviewer

• Due to how features are currently linked in plans & subscriptions, logically speaking a feature can rarely be archived once its used in the productcatalog/subscription subsystem. I added a ticket to clean this up at a later point (might even make sense to do away with "archiving" for features)