Only fetch steps and trigger for the current workflow version (#15003)

Avoid fetching full steps and trigger for versions that are not the
current version. Because those won't be used anyway. Better for
performances.

Only difficulty was for the `createDraft` mutation. I needed to return
the full created version so I can store it in cache and use it as new
`currentVersion`. Otherwise the current version is considered as
incomplete for a short time, since workflow is fetched separately from
the current version.

---------

Co-authored-by: Charles Bochet <charles@twenty.com>

packages/twenty-front/src/modules/object-record/utils/computeOptimisticRecordFromInput.ts

@@ -157,19 +157,6 @@ export const computeOptimisticRecordFromInput = ({
         continue;
       }
 
-      const relationIdFieldMetadataItem = objectMetadataItem.fields.find(
-        (field) => field.name === relationFieldIdName,
-      );
-
-      if (
-        !isDefined(relationIdFieldMetadataItem) &&
-        !isDefined(fieldMetadataItem.settings?.joinColumnName)
-      ) {
-        throw new Error(
-          'Should never occur, encountered unknown relationId within relations definitions',
-        );
-      }
-
       if (isNull(recordInputFieldIdValue)) {
         optimisticRecord[relationFieldIdName] = null;
         optimisticRecord[fieldMetadataItem.name] = null;