[source-amazon-seller-partner] VendorOrdersStatus stream fails with "cursor does not exist in the schema: createdBefore"

### Connector Name

source-amazon-seller-partner

### Connector Version

5.7.4

### What step the error happened?

During the sync

### Relevant information

**Summary**
The VendorOrdersStatus stream in the Amazon Selling Partner source connector fails on connection initialization because its default cursor field (`createdBefore`) does not exist in the stream's schema. `createdBefore` appears to be an Amazon SP API query parameter, not a response field, so it cannot be used as a cursor for incremental sync with deduplication.

**Steps to reproduce**
1. Set up a source-amazon-seller-partner connection (version 5.7.4)
2. Create a connection with VendorOrdersStatus enabled
3. Set sync mode to Incremental | Append + Deduped (the UI default)
4. Run the sync

**Expected behavior**
The VendorOrdersStatus stream syncs successfully, OR the UI prevents selecting a cursor field that isn't in the stream schema, OR the default cursor is set to a field that actually exists in the stream.

**Actual behavior**
The destination connector fails to initialize with: "For stream raw_amazon_selling_partner_us.VendorOrdersStatus: The cursor does not exist in the schema: createdBefore"

The sync fails before any records are emitted. Other streams in the same connection appear to be unaffected.

**Workaround**
Disabling the VendorOrdersStatus stream allows the rest of the connection to sync successfully.

**Environment**
- Airbyte deployment: self-hosted via abctl on GCE (Ubuntu 24.04)
- Airbyte version: 2.1.0
- Source connector: source-amazon-seller-partner (version 5.7.4)
- Destination: BigQuery (version 3.0.18)

### Relevant log output

```shell
2026-05-04 12:50:00 destination ERROR Caused by: io.airbyte.cdk.ConfigErrorException: For stream raw_amazon_selling_partner_us.VendorOrdersStatus: The cursor does not exist in the schema: createdBefore
2026-05-04 12:50:00 destination ERROR at io.airbyte.cdk.load.command.DestinationCatalog.throwIfInvalidDedupConfig$io_airbyte_airbyte_cdk_bulk_toolkits_bulk_cdk_toolkit_legacy_task_loader(DestinationCatalog.kt:84)
2026-05-04 12:50:00 destination ERROR at io.airbyte.cdk.load.command.DestinationCatalog.(DestinationCatalog.kt:47)
2026-05-04 12:50:00 destination ERROR at io.airbyte.cdk.load.command.DefaultDestinationCatalogFactory.getDestinationCatalog(DestinationCatalog.kt:132)

Full failure summary from the sync:

failureOrigin: destination
failureType: config_error
internalMessage: io.airbyte.cdk.ConfigErrorException: Failed to initialize connector operation
externalMessage: Failed to initialize connector operation
```

### Contribute

- [ ] Yes, I want to contribute

---
**Internal Tracking:** https://github.com/airbytehq/oncall/issues/12176