fix: retry on alreadyReplaced error

[ldez]

Fixes #2474

related to ietf-wg-acme/acme-ari#56

[ldez]

I have a problem: the RFC is talking about alreadyReplaced type

• https://datatracker.ietf.org/doc/html/draft-ietf-acme-ari-08#section-5
• https://datatracker.ietf.org/doc/html/draft-ietf-acme-ari-08#section-7.4

But Boulder has no reference of that: alreadyReplaced

letsencrypt/boulder#7385

And Pebble has also no reference: Conflict

Also, the type inside the issue is urn:ietf:params:acme:error:conflict and not urn:ietf:params:acme:error:alreadyReplaced.

So I don't know if I should follow the RFC.

@dmke WDYT?

[ldez]

Maybe @beautifulentropy could help us in this context?

[dmke]

Hm. I need to think about that a bit.

My gut feeling says go with the standard (even though it's still a draft).

[beautifulentropy]

@dmke @ldez Thanks for bringing this to my attention. It appears that we've dropped the ball here, I'll see about getting a PR out to fix this issue in Boulder and ensure that we reference this PR.

[beautifulentropy]

The aforementioned PR has been merged and should go to production next week. Thanks again for letting us know!

[ldez]

Thank you!
We will merge the PR, now we know we should follow the RFC.