Remove @_retry decorator for _api_check

[mikemhenry]

Since _api_check is in a private name space and isn't used except by unit tests + sys admins, I rather it just fail fast then keep trying. For example, I've got a deployment where I've got something misconfigured with S3, so when I call _api_check() I have to wait for the retry logic to run its course.

Other ideas:

• allow _retry to accept kwargs/options so we could make the retry happen with a faster time out, but still try a few times before we just report the error code to the user
• allow _api_check to take in an argument that disables retry logic

[dotsdl]

You can set the number of retries to 0 on the AlchemiscaleClient on init with max_retries=0. Also, could set after init with client.max_retries = 0.

Does that meet your needs?