Allow websockets for extensions

[joaoantoniocardoso]

This is a less strict approach than #3947: extensions can normally use upgrade headers (from 1.1) and have WebSocket running with extensionsv2, without any ties to a specific path.

Resulting config:

[github-actions]

Automated PR Review

0. Summary

• Verdict: LGTM

Adds the three standard nginx WebSocket upgrade headers (proxy_http_version 1.1, Upgrade $http_upgrade, Connection "Upgrade") to the generated /extensionv2/{name}/ location block in core/services/helper/main.py:481, so extensions running behind the helper's reverse-proxy config can use WebSockets. The pattern matches the convention already established in core/tools/nginx/nginx.conf for /webrtc/ws/, /network-test/, /system-information/, /terminal/, /zenoh/, and /zenoh-api/.

No further comments, nice job 👍

Generated by PR Review Bot. This is advisory, a human reviewer must still approve.