Wrapped the raw esbuild build error in a domain-specific `LogicFunctionException` with a new `LOGIC_FUNCTION_BUILD_FAILED` exception code. Previously, esbuild build failures from user code (syntax errors, unsupported features) propagated as unhandled `Error` instances all the way to Sentry, creating noise for what is fundamentally a user input validation issue — not an application bug.
Changes:
1. **`logic-function.exception.ts`** — Added `LOGIC_FUNCTION_BUILD_FAILED` enum value and its user-friendly message ("Function build failed. Please check your code for syntax errors.")
2. **`logic-function-graphql-api-exception-handler.utils.ts`** — Added `LOGIC_FUNCTION_BUILD_FAILED` to the switch case so it's handled as a known exception type (re-thrown as-is, same pattern as `CREATE_FAILED` and `INVALID_SEED_PROJECT`)
3. **`logic-function-resource.service.ts`** — Wrapped the `await build()` call in a try/catch that converts esbuild errors into `LogicFunctionException` with the build error message preserved for debugging