Temporarily hide Profiles functionality from UI
Without #1331 (closed), the Profiles functionality introduced in #764 (closed) is not likely to actually create value for our users since most data sources do not actually play well with data from multiple profiles ending up in the same analytics database, and there's no way for a user to know whether the extractor they're using is or isn't compatible.
We should hide the Profiles functionality from the interface until #1331 (closed) is resolved, and documentation is in place (#1353 (closed)), so that users can consistently get to value instead of confusion / unusable mixed data.
If a profile has already been set up, we can continue to allow the user to edit it, but a totally new user should not know that Profiles exist yet.