feat(nestjs): Support WebSocket errors in SentryGlobalFilter

[psh4607]

Before submitting a pull request, please take a look at our
Contributing guidelines and verify:

• If you've added code that should be tested, please add tests.
• Ensure your code lints and the test suite passes (yarn lint) & (yarn test).
• Link an issue if there is one related to your pull request. If no issue is linked, one will be auto-generated and linked.

Fixes #16067

SentryGlobalFilter now handles WebSocket exceptions without delegating them to Nest's HTTP BaseExceptionFilter.

Unexpected gateway errors are captured with the auto.ws.nestjs.global_filter mechanism and emit a generic error response. Expected WsException responses are preserved without being reported to Sentry. WsException is detected by shape so @nestjs/websockets does not become a required dependency.

Unit and NestJS WebSocket E2E coverage was added for unexpected errors, expected WsException values, and HTTP exceptions raised in a WebSocket context.

Root cause: WebSocket exceptions were delegated to an HTTP exception filter which expects an HTTP adapter and cannot correctly respond through a WebSocket client.

[chargome]

Looks good overall, just some minor nits.

[chargome]

Suggested change

	value: 'This is an exception in a WebSocket handler',
	value: 'This is an exception in a WebSocket handler',
	mechanism: {
	handled: false,
	type: 'auto.ws.nestjs.global_filter',
	},

[chargome]

Suggested change

	const client = host.switchToWs().getClient<{ emit: (event: string, data: unknown) => void }>();
	const client = host.switchToWs().getClient<{ emit?: (event: string, data: unknown) => void }>();

Let's put the emit function optional here, in case a user uses a ws adapter that is not compatible to this interface.