[Access] Configure ws connection in ws controller

[UlyanaAndrukhiv]

Closes: #6638

Context

This PR implements the initial WebSocket connection configuration for the new WebSocket controller. The changes focus on setting up timeouts and ensuring the connection remains responsive, preventing the server from blocking indefinitely while waiting for the client to send or receive messages:

• configureConnection:
  Sets an initial read deadline to prevent waiting indefinitely for a pong message.
  Establishes a Pong handler that resets the read deadline each time a pong is received, keeping the connection alive.

• Write Deadline Timeout:
  Adds SetWriteDeadline to ensure write operations time out if not completed within writeWait, preventing resource exhaustion from slow or unresponsive clients.

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 50.00000% with 17 lines in your changes missing coverage. Please review.

Project coverage is 41.22%. Comparing base (8a3055c) to head (04e392c).

Files with missing lines	Patch %	Lines
engine/access/rest/websockets/controller.go	46.42%	11 Missing and 4 partials ⚠️
...access/rest/websockets/legacy/websocket_handler.go	66.66%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #6750      +/-   ##
==========================================
- Coverage   41.26%   41.22%   -0.04%     
==========================================
  Files        2061     2061              
  Lines      182702   182728      +26     
==========================================
- Hits        75384    75333      -51     
- Misses     101010   101077      +67     
- Partials     6308     6318      +10     

Flag	Coverage Δ
unittests	41.22% <50.00%> (-0.04%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[illia-malachyn]

Can we also set a close handler here?

[UlyanaAndrukhiv]

I guess that we should think aboutclose handler as part of our error handling subtask. The default close handler sends a close message back to the peer.

func (c *Conn) SetCloseHandler(h func(code int, text string) error) {
	if h == nil {
		h = func(code int, text string) error {
			message := FormatCloseMessage(code, "")
			c.WriteControl(CloseMessage, message, time.Now().Add(writeWait))
			return nil
		}
	}
	c.handleClose = h
}

https://github.com/gorilla/websocket/blob/5e002381133d322c5f1305d171f3bdd07decf229/conn.go#L1146-L1156

[Guitarheroua]

Let`s put this in #6642 just not to forget it.

[Guitarheroua]

Looks good to me!

[illia-malachyn]

LGTM! Let's add tests for this in this PR as they're related #6757

[UlyanaAndrukhiv]

This changes is included into PR #6757