Registry API Refactoring (#144)

* Refactor core to use a flexible registry pattern

- Introduce a new registry mechanism for mailer providers
- Extract mailer provider enum to a separate file
- Implement dynamic mailer loading using a registry
- Update package dependencies and exports
- Improve modularity and extensibility of mailer implementation

* Refactor monitoring and billing services to use a flexible registry pattern

- Introduce a shared registry mechanism for dynamic service loading
- Replace static switch-based implementations with a registry-based approach
- Update instrumentation, CMS, and monitoring services to use the new registry
- Improve modularity and extensibility of service implementations
- Add Zod-based type-safe provider validation

* Simplify async registration in monitoring and billing services

- Remove unnecessary async wrappers for no-op registrations
- Update type definitions to support both async and sync registration functions
- Standardize registration approach for Paddle and Sentry providers

* Remove Tailwind package from packages where it is not being needed

* Remove Tailwind config references from pnpm-lock.yaml

* Update instrumentation registry to support dynamic monitoring providers

- Modify type definition to use NonNullable MonitoringProvider
- Import MonitoringProvider type from get-monitoring-provider
- Enhance type safety for instrumentation registration

packages/monitoring/api/src/instrumentation.ts

@@ -1,37 +1,51 @@
-import { getMonitoringProvider } from './get-monitoring-provider';
-import { InstrumentationProvider } from './monitoring-providers.enum';
+import { createRegistry } from '@kit/shared/registry';
 
-const PROVIDER = getMonitoringProvider();
+import {
+  MonitoringProvider,
+  getMonitoringProvider,
+} from './get-monitoring-provider';
+
+// Define a type for the instrumentation registration implementation
+type InstrumentationRegistration = {
+  register: () => Promise<void> | void;
+};
+
+// Create a registry for instrumentation providers, using literal strings 'baselime' and 'sentry'
+const instrumentationRegistry = createRegistry<
+  InstrumentationRegistration,
+  NonNullable<MonitoringProvider>
+>();
+
+// Register the 'baselime' instrumentation provider
+instrumentationRegistry.register('baselime', async () => {
+  const { registerInstrumentation } = await import(
+    '@kit/baselime/instrumentation'
+  );
+
+  return { register: registerInstrumentation };
+});
+
+// Register the 'sentry' instrumentation provider with a no-op registration, since Sentry v8 sets up automatically
+instrumentationRegistry.register('sentry', () => {
+  return {
+    register: () => {
+      return;
+    },
+  };
+});
 
 /**
  * @name registerMonitoringInstrumentation
- * @description Register monitoring instrumentation based on the MONITORING_PROVIDER environment variable.
- *
- * Please set the MONITORING_PROVIDER environment variable to register the monitoring instrumentation provider.
+ * @description Register monitoring instrumentation based on the MONITORING_PROVIDER environment variable using the registry internally.
  */
 export async function registerMonitoringInstrumentation() {
-  if (!PROVIDER) {
+  const provider = getMonitoringProvider();
+
+  if (!provider) {
     return;
   }
 
-  switch (PROVIDER) {
-    case InstrumentationProvider.Baselime: {
-      const { registerInstrumentation } = await import(
-        '@kit/baselime/instrumentation'
-      );
+  const instrumentation = await instrumentationRegistry.get(provider);
 
-      return registerInstrumentation();
-    }
-
-    case InstrumentationProvider.Sentry: {
-      // Sentry v8 automatically sets this up
-
-      return;
-    }
-
-    default:
-      throw new Error(
-        `Unknown instrumentation provider: ${process.env.NEXT_PUBLIC_MONITORING_PROVIDER}`,
-      );
-  }
+  return instrumentation.register();
 }