Cluster API: Improve probe method's error handling and retry logic in ManagedCluster class

[coderabbitai]

Description

This issue proposes improving the method in the class by:

1. Adding retry logic with exponential backoff for transient failures (network issues, timeouts)
2. Implementing more precise error type checking
3. Better handling for different error conditions

Suggested Implementation

• Add max_retries parameter (default 3)
• Implement exponential backoff for retries
• Distinguish between permanent errors and transient errors
• Only retry on network/connection-related issues
• Add improved logging for retry attempts

References

• Originally suggested in: SDK and CLI for CrateDB Cloud Cluster APIs #81 (comment)

Requested by

@amotl