Improve Logging for Queue Attributes Resolver

[tomazfernandes]

Usually the first time Spring Cloud AWS SQS tries to connect to AWS is through QueueAttributesResolver either for resolving attributes or the queue url.

Because of this, any connectivity issue is logged in this context, misleading users to think that the problem is with the default queue creation strategy, when it could really be any other reason.

While the original AWS SDK exception is also already logged, we could look into a better message to help users correctly identify the connection issue.

See #980 (comment)

[joseiedo]

Hey, Tomaz! I can make a PR for this issue.

What do you think about changing the QueueAttributesResolver.wrapException method by checking if the cause is an instance of software.amazon.awssdk.services.sqs.model.SqsException? If it is, we could add another message, such as:

<current message> + This might be due to connectivity issues with SQS or incorrect configuration.

Or do you think there's a better approach? Let me know!