[GSK-1698] Remove legacy ML worker info and properties

[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-1698 Adapt `giskard server expose` to the single exposed port

Previously we had to expose 2 ports: HTTP and TCP for worker connection

Now that workers connect through the same port as the UI we should adapt the giskard server expose command

[andreybavt]

@Inokinoki I see there are still places that mention ports 40051 and 50051 remaining. Could you clean them up completely to avoid confusion?

You can use this to search for remaining cases from the root of giskard repo:

grep "(ml.?)?worker.?(port|host)|40051|50051" * -riE

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information