fix: gosec issues

[lumtis]

Description

Fix the new gosec issues in the CI

Using nosec for false positive.
Adding timeout for websocket server.

Need confirmation for the following values:

• read timeout - 15sec
• write timeout - 15sec
• idle timeout - 1 minute

Pinging @zeta-chain/devops in case

Closes: #1288

[github-actions]

!!!WARNING!!!
nosec detected in the following files: rpc/websockets.go, x/emissions/client/tests/suite.go, x/observer/module_simulation.go

Be very careful about using #nosec in code. It can be a quick way to suppress security warnings and move forward with development, it should be employed with caution. Suppressing warnings with #nosec can hide potentially serious vulnerabilities. Only use #nosec when you're absolutely certain that the security issue is either a false positive or has been mitigated in another way.

Only suppress a single rule (or a specific set of rules) within a section of code, while continuing to scan for other problems. To do this, you can list the rule(s) to be suppressed within the #nosec annotation, e.g: /* #nosec G401 */ or //#nosec G201 G202 G203
Broad #nosec annotations should be avoided, as they can hide other vulnerabilities. The CI will block you from merging this PR until you remove #nosec annotations that do not target specific rules.

Pay extra attention to the way #nosec is being used in the files listed above.

[ws4charlie]

I'm not 100% sure if the idleTimeout will impact log filter users. We can give it a try and see.

[lumtis]

I'm not 100% sure if the idleTimeout will impact log filter users. We can give it a try and see.

Maybe we can increase it to 5min?