Guard yarn database:migrate:prod (#19008)

## Motivations
A lot of self hosters hands up using the `yarn database:migrated:prod`
either manually or through AI assisted debug while they try to upgrade
an instance while their workspace is still blocked in a previous one
Leading to their whole database permanent corruption

## What happened
Replaced the direct call the the typeorm cli to a command calling it
programmatically, adding a layer of security in case a workspace seems
to be blocked in a previous version than the one just before the one
being installed ( e.g 1.0 when you try to upgrade from 1.1 to 1.2 )

For our cloud we still need a way to bypass this security explaining the
-f flag

## Remark
Centralized this logic and refactored creating new services
`WorkspaceVersionService` and `CoreEngineVersionService` that will
become useful for the upcoming upgrade refactor

Related to https://github.com/twentyhq/twenty-infra/pull/529

packages/twenty-server/src/database/scripts/setup-db-utils.ts

@@ -0,0 +1,34 @@
+import { rawDataSource } from 'src/database/typeorm/raw/raw.datasource';
+
+export const camelToSnakeCase = (str: string) =>
+  str.replace(/[A-Z]/g, (letter) => `_${letter.toLowerCase()}`);
+
+export const performQuery = async <T = unknown>(
+  query: string,
+  consoleDescription: string,
+  withLog = true,
+  ignoreAlreadyExistsError = false,
+) => {
+  try {
+    const result = await rawDataSource.query<T>(query);
+
+    if (withLog) {
+      // oxlint-disable-next-line no-console
+      console.log(`Performed '${consoleDescription}' successfully`);
+    }
+
+    return result;
+  } catch (err) {
+    let message = '';
+
+    if (ignoreAlreadyExistsError && `${err}`.includes('already exists')) {
+      message = `Performed '${consoleDescription}' successfully`;
+    } else {
+      message = `Failed to perform '${consoleDescription}': ${err}`;
+    }
+    if (withLog) {
+      // oxlint-disable-next-line no-console
+      console.error(message);
+    }
+  }
+};