[client] Fix error handling case of flow grpc error

[pappz]

Describe your changes

When a gRPC error occurs in the Flow package, it will be propagated to the upper layers and handled similarly to a Management gRPC error.

• Always report a disconnected state in the event of any error
• Hide the underlying gRPC errors
• Force close the gRPC connection in the event of any error

Issue ticket number and link

Stack

Checklist

• Is it a bug fix
• Is a typo/documentation fix
• Is a feature enhancement
• It is a refactor
• Created tests that fail without the change (if possible)
• Extended the README / documentation, if necessary

[Copilot]

Pull Request Overview

This PR fixes the gRPC error handling in the Flow package by ensuring that any error from the stream is correctly propagated while also hiding underlying gRPC error details. In addition, it now closes the gRPC connection if it isn’t already shut down and triggers a disconnection notification on encountering an error.

• Propagate stream errors after attempting to close the connection
• Centralize the call to notifyDisconnected in the error branch of the stream handler
• Wrap error return values in receiveEvents to hide gRPC error codes

Comments suppressed due to low confidence (1)

management/client/grpc.go:270

• [nitpick] Wrapping the error with fmt.Errorf using only the error message may obscure useful debugging context. Consider using error wrapping with '%w' or adding context if that aligns with the intent to hide underlying gRPC error details.

return fmt.Errorf("%v", err.Error())

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud