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/views/view-picker/components/ViewPickerOptionDropdown.tsx

@@ -8,6 +8,7 @@ import { View } from '@/views/types/View';
 import { useDeleteViewFromCurrentState } from '@/views/view-picker/hooks/useDeleteViewFromCurrentState';
 import { useViewPickerMode } from '@/views/view-picker/hooks/useViewPickerMode';
 import { viewPickerReferenceViewIdComponentState } from '@/views/view-picker/states/viewPickerReferenceViewIdComponentState';
+import { useLingui } from '@lingui/react/macro';
 import { useState } from 'react';
 import {
   IconHeart,
@@ -17,7 +18,6 @@ import {
   MenuItem,
   useIcons,
 } from 'twenty-ui';
-import { useLingui } from '@lingui/react/macro';
 
 type ViewPickerOptionDropdownProps = {
   isIndexView: boolean;
@@ -46,7 +46,8 @@ export const ViewPickerOptionDropdown = ({
   const { createFavorite } = useCreateFavorite();
 
   const isFavorite = favorites.some(
-    (favorite) => favorite.recordId === view.id && favorite.workspaceMemberId,
+    (favorite) =>
+      favorite.recordId === view.id && favorite.forWorkspaceMemberId,
   );
 
   const handleDelete = () => {