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-front/src/modules/favorites/utils/sortFavorites.ts

@@ -27,7 +27,10 @@ export const sortFavorites = (
 ) => {
   return favorites
     .map((favorite) => {
-      if (isDefined(favorite.viewId) && isDefined(favorite.workspaceMemberId)) {
+      if (
+        isDefined(favorite.viewId) &&
+        isDefined(favorite.forWorkspaceMemberId)
+      ) {
         const view = views.find((view) => view.id === favorite.viewId);
 
         if (!isDefined(view)) {
@@ -54,7 +57,7 @@ export const sortFavorites = (
             { objectNamePlural: labelPlural.toLowerCase() },
             favorite.viewId ? { viewId: favorite.viewId } : undefined,
           ),
-          workspaceMemberId: favorite.workspaceMemberId,
+          forWorkspaceMemberId: favorite.forWorkspaceMemberId,
           favoriteFolderId: favorite.favoriteFolderId,
           objectNameSingular: 'view',
           Icon: view?.icon,
@@ -86,7 +89,7 @@ export const sortFavorites = (
             link: hasLinkToShowPage
               ? objectRecordIdentifier.linkToShowPage
               : '',
-            workspaceMemberId: favorite.workspaceMemberId,
+            forWorkspaceMemberId: favorite.forWorkspaceMemberId,
             favoriteFolderId: favorite.favoriteFolderId,
             objectNameSingular: objectNameSingular,
           } as ProcessedFavorite;