Figure Solution for concurrent updates errors

[Jonathan-Zollinger]

Description:
When dispatching multiple reactive update requests to the identical Zendesk entity (e.g., the same Ticket ID) simultaneously, the requests may fail due to optimistic locking on the Zendesk backend.

Error Message:
503 error
{"message":"Service is temporarily unavailable because of a concurrent update. Please try again."}

Steps to Reproduce:

1. Create a Flux of multiple update payloads targeting the same resource ID.
2. Execute the requests concurrently (e.g., using .flatMap()).
3. Observe the error response from the Zendesk API.

This should be a similar strategy to dealing with 429 errors