Enhance role-check system with stricter checks (#15392)

## Overview

This PR strengthens our permission system by introducing more granular
role-based access control across the platform.

## Changes

### New Permissions Added
- **Applications** - Control who can install and manage applications
- **Layouts** - Control who can customize page layouts and UI structure
- **AI** - Control access to AI features and agents
- **Upload File** - Separate permission for file uploads
- **Download File** - Separate permission for file downloads (frontend
visibility)

### Security Enhancements
- Implemented whitelist-based validation for workspace field updates
- Added explicit permission guards to core entity resolvers
- Enhanced ESLint rule to enforce permission checks on all mutations
- Created `CustomPermissionGuard` and `NoPermissionGuard` for better
code documentation

### Affected Components
- Core entity resolvers: webhooks, files, domains, applications,
layouts, postgres credentials
- Workspace update mutations now use whitelist validation
- Settings UI updated with new permission controls

### Developer Experience
- ESLint now catches missing permission guards during development
- Explicit guard markers make permission requirements clear in code
review
- Comprehensive test coverage for new permission logic

## Testing
- ✅ All TypeScript type checks pass
- ✅ ESLint validation passes
- ✅ New permission guards properly enforced
- ✅ Frontend UI displays new permissions correctly

## Migration Notes
Existing workspaces will need to assign the new permissions to roles as
needed. By default, all new permissions are set to `false` for non-admin
roles.

packages/twenty-server/src/engine/metadata-modules/view-field/exceptions/view-field.exception.ts

@@ -17,6 +17,7 @@ export class ViewFieldException extends CustomException {
 
 export enum ViewFieldExceptionCode {
   VIEW_FIELD_NOT_FOUND = 'VIEW_FIELD_NOT_FOUND',
+  VIEW_NOT_FOUND = 'VIEW_NOT_FOUND',
   INVALID_VIEW_FIELD_DATA = 'INVALID_VIEW_FIELD_DATA',
 }
 
@@ -24,6 +25,7 @@ export enum ViewFieldExceptionMessageKey {
   WORKSPACE_ID_REQUIRED = 'WORKSPACE_ID_REQUIRED',
   VIEW_ID_REQUIRED = 'VIEW_ID_REQUIRED',
   VIEW_FIELD_NOT_FOUND = 'VIEW_FIELD_NOT_FOUND',
+  VIEW_NOT_FOUND = 'VIEW_NOT_FOUND',
   INVALID_VIEW_FIELD_DATA = 'INVALID_VIEW_FIELD_DATA',
   FIELD_METADATA_ID_REQUIRED = 'FIELD_METADATA_ID_REQUIRED',
   VIEW_FIELD_ALREADY_EXISTS = 'VIEW_FIELD_ALREADY_EXISTS',
@@ -40,6 +42,8 @@ export const generateViewFieldExceptionMessage = (
       return 'ViewId is required';
     case ViewFieldExceptionMessageKey.VIEW_FIELD_NOT_FOUND:
       return `View field${id ? ` (id: ${id})` : ''} not found`;
+    case ViewFieldExceptionMessageKey.VIEW_NOT_FOUND:
+      return `View${id ? ` (id: ${id})` : ''} not found`;
     case ViewFieldExceptionMessageKey.INVALID_VIEW_FIELD_DATA:
       return `Invalid view field data${id ? ` for view field id: ${id}` : ''}`;
     case ViewFieldExceptionMessageKey.FIELD_METADATA_ID_REQUIRED: