chore: improve monitoring for NULL bytes in REST API input cause PostgreSQL reje

### Monitoring Fix: Include PostgreSQL error code in Sentry exception messages

**File:** `http-exception-handler.service.ts`

For `PostgresException` instances that still reach the 500 handler (non-22xxx errors like constraint violations, syntax errors, etc.), the exception message now includes the PostgreSQL error code: `"Data validation error. (PG error code: 42703)"`.

**Before:** Sentry showed only `InternalServerErrorException: Data validation error.` with no way to distinguish between different PostgreSQL error types without reading source code.

**After:** The PG error code is embedded in the Sentry error title, enabling:
- Better Sentry issue grouping by error code
- Faster triage — engineers can immediately identify the error class (23xxx = constraint, 42xxx = syntax/schema, 53xxx = resources)
- Easier correlation with PostgreSQL documentation

packages/twenty-server/src/engine/core-modules/exception-handler/http-exception-handler.service.ts

@@ -105,7 +105,9 @@ export class HttpExceptionHandlerService {
     }
 
     if (exception instanceof PostgresException) {
-      exception = new InternalServerErrorException(exception.message);
+      exception = new InternalServerErrorException(
+        `${exception.message} (PG error code: ${exception.code})`,
+      );
       statusCode = 500;
     }
 

packages/twenty-server/src/engine/twenty-orm/error-handling/compute-twenty-orm-exception.ts

@@ -51,9 +51,9 @@ export const computeTwentyORMException = async (
       );
     }
 
-    if (errorCode === POSTGRESQL_ERROR_CODES.INVALID_TEXT_REPRESENTATION) {
+    if (isDefined(errorCode) && errorCode.startsWith('22')) {
       return new TwentyORMException(
-        error.message, // safe and useful
+        error.message,
         TwentyORMExceptionCode.INVALID_INPUT,
       );
     }