Removed currentCountQuery from limitAnalytics

ref BAE-336
ref BAE-330

This was a working approach, but in order to achieve grandfathering we'll try overwriting the limit at the source in Zuul by adding a limit specific cohort with all site IDs that are currently using the feature and will be affected by the limit, so they can be grandfathered and keep using it.

Author: aileen

packages/limit-service/lib/config.js

@@ -57,17 +57,6 @@ module.exports = {
         formatter: count => `${count / 1000000}MB`
     },
     limitStripeConnect: {},
-    limitAnalytics: {
-        currentCountQuery: async (knex) => {
-            const key = 'trafficAnalytics';
-            const settings = await knex('settings');
-            const setting = settings.find(s => s.key === key);
-            const labSettings = settings.find(s => s.key === 'labs');
-            const labsSetting = labSettings && labSettings.value && labSettings.value[key];
-            const labsSettingEnabled = labsSetting === true;
-
-            return (setting && setting.value === 'true') || labsSettingEnabled;
-        }
-    },
+    limitAnalytics: {},
     limitActivityPub: {}
 };