When we used `limited?` we found the user was
prevented from completing their last chance at a
request, due to the `>=`, since the attempts and
max_attempts were equal.

Instead we needed a way to only prevent that if
the user had exceeded their max amount of tries.

In the previous commit, we were looking to prevent the
`capture_doc_status_controller` from setting the rate limit too early.

In this commit, we are instead removing the logic to even look at rate
limiting here, since [as Dawei pointed out](#10538 (comment)), and as I found [a past
discussion for](#9370 (comment)), this code should never be reached if rate limited.

…c when user is on last try

… test.