Refactor Multiple API Attempts Logic to Shared Method

Problem/Motivation

The logic to retry API requests when they fail is duplicated across several methods and some methods are missing it since the effort to implement it isn't nominal.

Is there value in wrapping this in the multiple tries logic we used elsewhere? If so, I would suggest abstracting the multiple tries into its own fetch function that can be used by this and the other requests?

— from @apotek a MR review

https://git.drupalcode.org/project/orange_dam/-/merge_requests/23#note_1...

Steps to reproduce

N/A

Proposed resolution

Create a method in the API class that allows for the fail/retry API functionality to be easily re-usable.

Remaining tasks

Figure out how to do this and build it.

User interface changes

N/A

API changes

N/A

Data model changes

N/A