fix(amazonq): add retries for /transform APIs

[dhasani23]

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

Description

Add back retries for /transform since they were being overridden to 0.

Checklist

• My code follows the code style of this project
• I have added tests to cover my changes
• A short description of the change has been added to the CHANGELOG if the change is customer-facing in the IDE.
• I have added metrics for my changes (if required)

License

I confirm that my contribution is made under the terms of the Apache 2.0 license.

[dhasani23]

I'm guessing the intention was to do 3 retries (after the initial attempt), meaning this should technically be set to 4, and naming it MAX_ATTEMPTS is more accurate.

[dhasani23]

Following the same retry strategy from:

aws-toolkit-jetbrains/plugins/amazonq/shared/jetbrains-community/src/software/aws/toolkits/jetbrains/services/amazonq/clients/AmazonQStreamingClient.kt

Lines 82 to 89 in ebece9d

	isRetryable = { e ->
	when (e) {
	is ValidationException,
	is ThrottlingException,
	is SdkException,
	is TimeoutException,
	-> true
	else -> false

in the ExportResultArchive (download) API

and added SocketTimeoutException (which is not a type of TimeoutException, so it needs to be explicitly listed here)

[dhasani23]

This onCheckAuth was disposing of our codeTransformationSessionContext which doesn't make sense to do. Better to just initiate the onReauthStarted flow which does:

aws-toolkit-jetbrains/plugins/amazonq/codetransform/jetbrains-community/src/software/aws/toolkits/jetbrains/services/codemodernizer/controller/CodeTransformChatController.kt

Line 608 in ebece9d

* Invoking this is equivalent to user clicking "reauthenticate" in the Chat when credentials expired.

instead of waiting/hoping for the user to click on the Re-authenticate button in the notification.