Fix orderBy, groupBy, and orderByForRecords on foreignKey (#15480)

For the variables orderBy (for findMany and groupBy), groupBy (for
groupBy) and orderByForRecords (for groupBy), we were wrongfully adding
the foreign key field (eg: pointOfContact) by its joinColumnName (eg:
pointOfContactId) as the variable key (eg. `orderBy: { pointOfContactId:
"AscNullsFirst" } }`. That broke because then this key is used to
identify the field in the parsers.

This went unnoticed because this order / group option is not very
interesting as it is limited to the id for now, but it s still better to
have it work than crash!

before (on findMany)
<img width="1841" height="674" alt="flawn_order_by_pocId"
src="https://github.com/user-attachments/assets/3ccd7604-041d-4b7e-8b6a-c1d268440a45"
/>

after (on findMany)
<img width="1182" height="805" alt="image"
src="https://github.com/user-attachments/assets/e9253683-bcbe-429e-bbef-e334c7cc76af"
/>

packages/twenty-server/src/engine/twenty-orm/utils/format-column-name-for-relation-field.util.ts

@@ -0,0 +1,19 @@
+import { RelationType } from 'twenty-shared/types';
+import { isDefined } from 'twenty-shared/utils';
+
+import { type FieldMetadataRelationSettings } from 'src/engine/metadata-modules/field-metadata/interfaces/field-metadata-settings.interface';
+
+export const formatColumnNameForRelationField = (
+  fieldName: string,
+  fieldMetadataSettings: FieldMetadataRelationSettings,
+): string => {
+  if (fieldMetadataSettings.relationType === RelationType.MANY_TO_ONE) {
+    if (!isDefined(fieldMetadataSettings.joinColumnName)) {
+      throw new Error(`Join column name is not defined for field ${fieldName}`);
+    }
+
+    return fieldMetadataSettings.joinColumnName;
+  }
+
+  return fieldName;
+};