Handle restricted objects #1 refactor permissions map + return object permissions from gql (#12313)

## Context
- Introduced objectPermissions in currentUserWorkspace which uses role
permissions from cache so we can fetch granular permissions from the API
- Refactored cached role permissions to map permissions with object
metadata id instead of object metadata name singular to be more flexible

New Cache
<img width="574" alt="Screenshot 2025-05-27 at 11 59 06"
src="https://github.com/user-attachments/assets/1a090134-1b8a-4681-a630-29f1472178bd"
/>

GQL
<img width="977" alt="Screenshot 2025-05-27 at 11 58 53"
src="https://github.com/user-attachments/assets/3b9a82b0-6019-4a25-a6e2-a9e0fb4bb8a0"
/>


Next steps: Use the updated API in the FE to fetch granular permissions
and update useHasObjectReadOnlyPermission hook

packages/twenty-server/test/integration/graphql/suites/settings-permissions/roles.integration-spec.ts

@@ -478,8 +478,6 @@ describe('roles permissions', () => {
       }) => `
       mutation UpsertObjectPermissions {
           upsertObjectPermissions(upsertObjectPermissionsInput: { roleId: "${roleId}", objectPermissions: [{objectMetadataId: "${objectMetadataId}", canUpdateObjectRecords: true}]}) {
-              id
-              roleId
               objectMetadataId
               canUpdateObjectRecords
           }
@@ -541,7 +539,6 @@ describe('roles permissions', () => {
             expect(res.body.data.upsertObjectPermissions).toEqual(
               expect.arrayContaining([
                 expect.objectContaining({
-                  roleId: createdEditableRoleId,
                   objectMetadataId: listingObjectId,
                   canUpdateObjectRecords: true,
                 }),