feat: extract retry config from resources and added default retry config

[hqhqhqhqhqhqhqhqhqhqhq]

This pr extract the repetitive code in setting up client with retry and added default retry configs when custom retry logics not provided.
Also solves #691

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

Files not reviewed (7)

• internal/services/common.go: Evaluated as low risk
• internal/services/azapi_resource_action_ephemeral.go: Evaluated as low risk
• internal/services/azapi_resource_action_resource.go: Evaluated as low risk
• internal/services/azapi_resource_list_data_source.go: Evaluated as low risk
• internal/services/azapi_resource_action_data_source.go: Evaluated as low risk
• internal/services/azapi_resource_data_source.go: Evaluated as low risk
• internal/retry/retryable_errors.go: Evaluated as low risk

Comments suppressed due to low confidence (2)

internal/clients/data_plane_client.go:544

• Ensure that the input to StringSliceToRegexpSliceMust is always valid to prevent panics from invalid regex patterns.

errRegExps = StringSliceToRegexpSliceMust(retry.GetErrorMessages())

internal/clients/data_plane_client.go:557

• Add a test case to verify that RetryGet correctly handles the environment variable and falls back to the default value if the variable is not set or invalid.

return 2 * time.Minute

[matt-FFFFFF]

The retry for the get after put is a special case and does not use the configuration in the resource's retry attribute. Removing the above code will cause a regression for resources deployed at MG scope, as this relies on the response check function:

			func(d interface{}) bool {
				return d == nil
			},