Enhance error handling in .Stop() methods in queues

[kirugan]

No description provided.

[Copilot]

Pull Request Overview

This PR enhances error handling in the Stop() methods by collecting and returning all errors instead of failing fast on the first error encountered. The change ensures that cleanup operations continue even if one component fails to stop properly.

• Changed Stop() methods to collect all errors instead of returning immediately on first error
• Used errors.Join() to combine multiple errors into a single return value
• Ensures both queue components attempt to stop regardless of individual failures

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
queuemngr/queue_manager.go	Modified Stop() method to collect errors from both queues and return combined result
client/rabbitmq_client.go	Updated Stop() method to attempt closing both channel and connection, returning combined errors

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[kirugan]

One important note: errors.Join(...) returns nil in 2 cases:

1. when no arguments provided like: errors.Join(emptySlice...)
2. all arguments (=errors) are nil: errors.Join(nilErrorVar, someNilErrorVar)

[kirugan]

second case is what we have here