Data changes to prepare for workspaceMember page (#10439)

Workspace Member will get their own record page in the future.

This PR lays backend changes to prepare for this:
- Settings most fields on WorkspaceMember as system fields
- Renaming workspaceMember/workspaceMemberId to
forWorkspaceMember/forWorkspaceMemberId as it conflicts with the morph
relationship, if we want to be able to add a workspace member as
favorite

---------

Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>

packages/twenty-server/src/modules/favorite/standard-objects/favorite.workspace-entity.ts

@@ -53,7 +53,7 @@ export class FavoriteWorkspaceEntity extends BaseWorkspaceEntity {
 
   // Relations
   @WorkspaceRelation({
-    standardId: FAVORITE_STANDARD_FIELD_IDS.workspaceMember,
+    standardId: FAVORITE_STANDARD_FIELD_IDS.forWorkspaceMember,
     type: RelationMetadataType.MANY_TO_ONE,
     label: msg`Workspace Member`,
     description: msg`Favorite workspace member`,
@@ -62,10 +62,10 @@ export class FavoriteWorkspaceEntity extends BaseWorkspaceEntity {
     inverseSideTarget: () => WorkspaceMemberWorkspaceEntity,
   })
   @WorkspaceIsNullable()
-  workspaceMember: Relation<WorkspaceMemberWorkspaceEntity>;
+  forWorkspaceMember: Relation<WorkspaceMemberWorkspaceEntity>;
 
-  @WorkspaceJoinColumn('workspaceMember')
-  workspaceMemberId: string;
+  @WorkspaceJoinColumn('forWorkspaceMember')
+  forWorkspaceMemberId: string;
 
   @WorkspaceRelation({
     standardId: FAVORITE_STANDARD_FIELD_IDS.person,