New tables without replication_key column breaks replication

We apply the following config so that we automatically replicate new tables:

      select:
        - '*.*'
      metadata:
        '*':
          replication-key: updated_at
          updated_at:
            is-replication-key: true

If a new table does not have updated_at column, the whole tap errors out and our pipeline stays broken until we add a manual override:

        public-table:
          replication-key: created_at
          created_at:
            is-replication-key: true

        public-other_table:
          replication-method: FULL_TABLE
          replication-key: ''

We should be able to configure a fallback behavior in these cases, such as a warning

No files or tests are named. Start by tracing how select and metadata replication-key settings are applied when a newly discovered table lacks updated_at. Define and test a fallback that warns or selects an alternate replication behavior without stopping the tap, including the existing manual override cases.