Limit DB Usage Based on Plan

[tpjnorton]

Kind of a coda to #100.

Right now all plans have access to all features.

However there are some features that will create very large numbers of database rows (release task events, for example), that won't be visible to some product tiers anyway, creating bloat for us and $$$ spent on infra for no reason.

Our goal right now is not to upsell free-tier users (much) to the mgr plan as they likely as artists won't be able to buy the product.

So any features that are "off" for the free plan should not exist in the database.

Preliminary List

• Release Task Events (comments, etc)
• Audit Log-type stuff
• Default Contact Labels for a workspace ? not too bad, like 20 rows per workspace at most

As we grow there'll likely be more stuff we need to manage here, but we just need to make sure we do this.

We really don't want 20M rows of data nobody is likely to see.