feat: add robust datetime parsing fallback to DatetimeBasedCursor

- Add ab_datetime_try_parse as fallback when expected formats fail
- Maintain backward compatibility by trying expected formats first
- Update schema documentation to reflect new fallback behavior
- Update test to use truly unparseable string for error case
- Preserve original cursor value format in state storage
- Eliminate parsing errors for ISO8601/RFC3339 compliant datetimes

Co-Authored-By: AJ Steers <[email protected]>

Author: devin-ai-integration[bot]

airbyte_cdk/sources/declarative/declarative_component_schema.yaml

@@ -944,7 +944,9 @@ definitions:
         items:
           type: string
         description: |
-          The possible formats for the cursor field, in order of preference. The first format that matches the cursor field value will be used to parse it. If not provided, the Outgoing Datetime Format will be used.
+          The possible formats for the cursor field, in order of preference. The first format that matches the cursor field value will be used to parse it.
+          If none of the specified formats match, the system will attempt to parse the value using robust datetime parsing that handles most ISO8601/RFC3339 compliant formats.
+          If not provided, the Outgoing Datetime Format will be used as the first attempt.
           Use placeholders starting with "%" to describe the format the API is using. The following placeholders are available:
             * **%s**: Epoch unix timestamp - `1686218963`
             * **%s_as_float**: Epoch unix timestamp in seconds as float with microsecond precision - `1686218963.123456`

airbyte_cdk/sources/declarative/incremental/datetime_based_cursor.py

@@ -21,6 +21,7 @@
 )
 from airbyte_cdk.sources.message import MessageRepository
 from airbyte_cdk.sources.types import Config, Record, StreamSlice, StreamState
+from airbyte_cdk.utils.datetime_helpers import ab_datetime_format, ab_datetime_try_parse
 from airbyte_cdk.utils.mapping_helpers import _validate_component_request_option_paths
 
 
@@ -313,6 +314,11 @@ def parse_date(self, date: str) -> datetime.datetime:
                 return self._parser.parse(date, datetime_format)
             except ValueError:
                 pass
+
+        parsed_dt = ab_datetime_try_parse(date)
+        if parsed_dt:
+            return parsed_dt
+
         raise ValueError(f"No format in {self.cursor_datetime_formats} matching {date}")
 
     @classmethod

unit_tests/sources/declarative/incremental/test_datetime_based_cursor.py

@@ -1021,7 +1021,7 @@ def test_given_unknown_format_when_parse_date_then_raise_error():
         parameters={},
     )
     with pytest.raises(ValueError):
-        slicer.parse_date("2021-01-01T00:00:00.000000+0000")
+        slicer.parse_date("not-a-valid-datetime-string")
 
 
 @pytest.mark.parametrize(