BREAKING CHANGE: Fix graphql errors (#12775)

We were using a global ValidationPipe in main.ts. This is an issue as
@Controllers should return HttpExecption and @Resolvers should return
GraphqlErrors

Removing the global pipe and creating a ResolverValidationPipe able to
generate GraphqlError. We also need to handle the exception in a filter
to avoid nest to think it's unhandled and make it flow to logs


Next step:
- it would be nice to have both @UsePipes(ResolverValidationPipe) +
@UseFilters(GraphqlValidationExceptionFilter) come together. This should
be possible if we create a @GraphQLResolver annotation

packages/twenty-front/src/modules/object-record/record-table/record-table-body/components/RecordTableBody.tsx

@@ -19,7 +19,7 @@ const StyledTbody = styled.tbody`
     tr:not(:last-child) td:nth-of-type(3) {
       // Last row is aggregate footer
       position: sticky;
-      left: 43px;
+      left: 39px;
       z-index: ${TABLE_Z_INDEX.cell.sticky};
       transition: transform 0.3s ease;
 

packages/twenty-front/src/modules/object-record/record-table/record-table-header/components/RecordTableHeader.tsx

@@ -40,7 +40,7 @@ const StyledTableHead = styled.thead`
 
     th:nth-of-type(3) {
       position: sticky;
-      left: 43px;
+      left: 39px;
       z-index: ${TABLE_Z_INDEX.header.default};
       transition: 0.3s ease;