fix(DATAGO-111857): improve error handling in SolaceMessaging by raising the original exception

[cyrus2281]

What is the purpose of this change?

Improve error handling in the SolaceMessaging component to ensure that the original exception is properly raised when creating a persistent receiver fails, making debugging and error handling more effective.

How is this accomplished?

• fix: improve error handling in SolaceMessaging by raising the original exception
  • Capture the PubSubPlusClientError as variable 'e' instead of letting it pass uncaptured
  • Raise the actual exception 'e' instead of an undefined 'exception' variable

Anything reviews should focus on/be aware of?

The fix addresses a bug where an undefined 'exception' variable was being raised, which would have caused a NameError rather than showing the actual underlying issue.