Replace log.Fatalf with error return in provider/server.go

[coderabbitai]

Context

In PR #860, a code review identified that provider/server.go calls log.Fatalf when gs.Serve(listen) returns an error (around lines 145-147). This exits the entire process and bypasses callers' control and cleanup logic.

Problem

log.Fatalf should not be used in library code as it prevents proper error handling and cleanup by callers.

Requested Change

The function should return the error to the caller instead of calling log.Fatalf, allowing the caller to handle cleanup appropriately.

References

• PR: ✨ Adding begining of socket communication #860
• Review Comment: ✨ Adding begining of socket communication #860 (comment)
• Requested by: @shawn-hurley

[konveyor-ci-bot]

This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members.