Add clarity for analytics only database columns
What does this MR do?
There were some recent limitations communicated about adding SAAS analytics columns to the database. It's come up again, and so we're trying to identify and clarify the policy we should have here before we tackle that work.
Generally, if we were a closed source SAAS product this wouldn't be a concern, but since we balance concerns between the SAAS product, and our Self-managed customers, we should probably be cognizant of how these requests for analytics columns might come across to all customers.
We probably want to leverage pushing this data into a system like snowplow, and dealing with the constraints we have there, instead of adding columns to our schema.