fix(sdk): remove update record not upserted (#149)

This is similar to #148 but for invalid update found in the example input.json.

Author: mumoshu

development-guide/destination-connector-development-guide.md

@@ -154,4 +154,7 @@ The following is a list of test scenarios we recommend you consider:
 Yes, definitely. This happens during the [initial sync](https://fivetran.com/docs/getting-started/glossary#initialsync) or a [re-sync](https://fivetran.com/docs/using-fivetran/features#resync) where the source connector first calls the `truncate` operation and then `upserts`. The `truncate` in this case is meant to (soft) delete any rows that may have existed prior to the initial sync starting. This is done to make sure all rows that may have existed prior to the initial sync are marked as deleted (since we cannot be sure the initial sync will necessarily overwrite them all). It should pick out the rows that existed prior to the sync starting, in other words, where `_fivetran_synced` < "timestamp when `truncate` is called in the source connector".
 
 ### What happens if a source connector sends a delete event for a record that was never upserted? 
-Deletes for records that were never upserted are safely ignored — no action should be taken.
+Deletes for records that were never upserted are safely ignored — no action should be taken.
+
+### What happens if a source connector sends an update event for a record that was never upserted?
+Updates for records that were never upserted are safely ignored — no action should be taken.

tools/destination-connector-tester/input-files/input.json

@@ -205,12 +205,6 @@
                   "amount_double": 400.555,
                   "flag": false,
                   "op_time": "2023-10-30T15:00:00Z"
-               },
-               {
-                  "id": 999,
-                  "amount_double": 0,
-                  "flag": false,
-                  "op_time": "2023-10-30T15:00:00Z"
                }
             ]
          }