Removed currentCountQuery from limit service config for customIntegrations

ref BAE-331
ref https://ghost.slack.com/archives/C02G9E68C/p1750776240012249

Since the introduction of the `customIntegrations` limit, it was been treated as a `Flag` limit, which is a simple on/off limit. The query that was assigned to in the config has never been executed and is not found in use anywhere in our repos.
To be able to let customers use a feature, which they have enabled, after we impose a limit for that feature, we're exploring the option to use `currentCountQuery` to overwrite the imposed limit if the feature is already being used. Having a query in the config for custom integrations messes with that idea, besides the fact that it's a pointless query.

Author: aileen

packages/limit-service/README.md

@@ -2,7 +2,7 @@
 This module is intended to hold **all of the logic** for testing if site:
 - would be over a given limit if they took an action (i.e. added one more thing, switched to a different limit)
 - if they are over a limit already
-- consistent error messages explaining why the limit has been reached 
+- consistent error messages explaining why the limit has been reached
 
 ## Install
 
@@ -54,7 +54,7 @@ const limits = {
         error: 'Email sending has been temporarily disabled whilst your account is under review.'
     },
     // following is a "max periodic" type of configuration
-    // note if you use this configuration, the limit service has to also get a 
+    // note if you use this configuration, the limit service has to also get a
     // "subscription" parameter to work as expected
     // emails: {
     //     maxPeriodic: 42,
@@ -69,7 +69,7 @@ const limits = {
 };
 
 // This information is needed for the limit service to work with "max periodic" limits
-// The interval value has to be 'month' as thats the only interval that was needed for
+// The interval value has to be 'month' as that's the only interval that was needed for
 // current usecase
 // The startDate has to be in ISO 8601 format (https://en.wikipedia.org/wiki/ISO_8601)
 const subscription = {
@@ -155,12 +155,12 @@ db.transaction((transacting) => {
 ### Types of limits
 At the moment there are four different types of limits that limit service allows to define. These types are:
 1. `flag` - is an "on/off" switch for certain feature. Example usecase: "disable all emails". It's identified by a `disabled: true` property in the "limits" configuration.
-2. `max` - checks if the maximum amount of the resource has been used up.Example usecase: "disable creating a staff user when maximum of 5 has been reached". To configure this limit add `max: NUMBER` to the configuration. The limits that support max checks are: `members`, `staff`, and `customIntegrations`
+2. `max` - checks if the maximum amount of the resource has been used up.Example usecase: "disable creating a staff user when maximum of 5 has been reached". To configure this limit add `max: NUMBER` to the configuration. The limits that support max checks are: `members`, and `staff`
 3. `maxPeriodic` - it's a variation of `max` type with a difference that the check is done over certain period of time. Example usecase: "disable sending emails when the sent emails count has acceded a limit for last billing period". To enable this limit define `maxPeriodic: NUMBER` in the limit configuration and provide a subscription configuration when initializing the limit service instance. The subscription object comes as a separate parameter and has to contain two properties: `startDate` and `interval`, where `startDate` is a date in  ISO 8601 format and period is `'month'` (other values like `'year'` are not supported yet)
-4. `allowList` - checks if provided value is defined in configured "allowlist". Example usecase: "disable theme activation if it is not an official theme". To configure this limit define ` allowlist: ['VALUE_1', 'VALUE_2', 'VALUE_N']` property in the "limits" parameter. 
+4. `allowList` - checks if provided value is defined in configured "allowlist". Example usecase: "disable theme activation if it is not an official theme". To configure this limit define ` allowlist: ['VALUE_1', 'VALUE_2', 'VALUE_N']` property in the "limits" parameter.
 
 ### Supported limits
-There's a limited amount of limits that are supported by limit service. The are defined by "key" property name in the "config" module. List of currently supported limit names: `members`, `staff`, `customIntegrations`, `emails`, `customThemes`, `uploads`. 
+There's a limited amount of limits that are supported by limit service. The are defined by "key" property name in the "config" module. List of currently supported limit names: `members`, `staff`, `customIntegrations`, `emails`, `customThemes`, `uploads`.
 
 All limits can act as `flag` or `allowList` types. Only certain (`members`, `staff`, and`customIntegrations`) can have a `max` limit. Only `emails` currently supports the `maxPeriodic` type of limit.
 
@@ -217,6 +217,6 @@ Follow the instructions for the top-level repo.
 
 
 
-# Copyright & License 
+# Copyright & License
 
 Copyright (c) 2013-2025 Ghost Foundation - Released under the [MIT license](LICENSE).

packages/limit-service/lib/config.js

@@ -45,16 +45,7 @@ module.exports = {
             return result.length;
         }
     },
-    customIntegrations: {
-        currentCountQuery: async (knex) => {
-            let result = await knex('integrations')
-                .count('id', {as: 'count'})
-                .whereNotIn('type', ['internal', 'builtin'])
-                .first();
-
-            return result.count;
-        }
-    },
+    customIntegrations: {},
     customThemes: {},
     uploads: {
         // NOTE: this function should not ever be used as for uploads we compare the size