Add forwardedRequestHeaders in routeTriggers (#17151)

- add `forwardedRequestHeaders` `string[]` column in `core.routeTrigger`
- filter request headers and forward filtered headers to function
payload (avoid spreading unexpectedly token or cookie)
- add `forwardedRequestHeaders` option in twenty-sdk `defineFunction`
util

BREAKING for actual routeTrigger payload but only 16 to migrate in
production

packages/twenty-sdk/src/cli/__tests__/test-app/src/app/test-function.function.ts

@@ -16,6 +16,7 @@ export default defineFunction({
       path: '/post-card/create',
       httpMethod: 'GET',
       isAuthRequired: false,
+      forwardedRequestHeaders: ['signature'],
     },
     {
       universalIdentifier: 'dd802808-0695-49e1-98c9-d5c9e2704ce2',

packages/twenty-sdk/src/cli/utils/__tests__/load-manifest.spec.ts

@@ -96,6 +96,7 @@ describe('loadManifest with test-app', () => {
     );
     expect(routeTrigger?.path).toBe('/post-card/create');
     expect(routeTrigger?.httpMethod).toBe('GET');
+    expect(routeTrigger?.forwardedRequestHeaders).toEqual(['signature']);
 
     const cronTrigger = testFunction.triggers.find((t) => t.type === 'cron');
     expect(cronTrigger).toBeDefined();