orange_dam 2.2.0

## New Features
1. Issue #3476559 by apotek: Allow for Logging of Search API queue requests. You can now subscribe to an OrangeDamApiResponseReceivedEvent, and, from the response object inside that event, extract all data from both the request and the response, so you can log and debug highly specific details about every interaction you have with the API, if desired.

2. Issue #3475689 by apotek: Allow for clock-sync-imperfections when asking for items modified since time during automated runs. This feature allows you to create a timestamp offset for the stored "changes since time" value, in order to patch over any clock-divergence between Orange DAM and your client's clock. For example, when a cron run causes a request to Orange DAM API for changes since the last stored "changes since time", items changed in the last second or two might get missed, depending on how closely aligned your client time is to Orange DAM. You can use the new `api_request_time_offset` orange_dam.setting to adjust the stored "since time" offset backwards (in seconds). An offset of 5 would adjust the "since time" to be recorded for the next query as five seconds earlier than it normally would have been. The upside is that you might catch content you might have missed otherwise. The downside is that you might request and queue the same item twice occasionally. We believe the upside outweighs the downside. Fortunately, you can set this offset to whatever you would like.

This release updates the required version of chromatic/orange-dam-php to version 2.