[GSK-1509] Add tests for ML worker actors behind WebSocket

[Inokinoki]

Description

Related Issue

Type of Change

• 📚 Examples / docs / tutorials / dependencies update
• 🔧 Bug fix (non-breaking change which fixes an issue)
• 🥂 Improvement (non-breaking change which improves an existing feature)
• 🚀 New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to change)
• 🔐 Security fix

Checklist

• I've read the CODE_OF_CONDUCT.md document.
• I've read the CONTRIBUTING.md guide.
• I've updated the code style using make codestyle.
• I've written tests for all new methods and classes that I created.
• I've written the docstring in Google format for all the methods and classes that I used.

[linear]

GSK-1509 Add integration tests for WebSocket communication

1. Java side integration test

   create a WebSocket endpoint, use a fake WebSocket connection to connect and test

2. Python-Java integration test

   replace callbacks with mock function, use test-container to create a backend. use ~requests~ to call Web interface, then assert the messages received

3. Python integration test

   how to test the implementations in listener.py ? - (testing with tests.utils.MockedClient should work)

[Inokinoki]

Depending on #1535

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

80.0% Coverage
0.0% Duplication