ccl/changefeedccl: TestChangefeedProtectedTimestampUpdateForMultipleTables failed

ccl/changefeedccl.TestChangefeedProtectedTimestampUpdateForMultipleTables [failed](https://mesolite.cluster.engflow.com/invocations/default/a52286ee-7a8d-420c-a276-393eaedbfb40?testReportRun=2&testReportShard=9&testReportAttempt=1#targets-Ly9wa2cvY2NsL2NoYW5nZWZlZWRjY2w6Y2hhbmdlZmVlZGNjbF90ZXN0) on master @ [bf01372d7ca0f2e6ad6dfa107d679182aee173dd](https://github.com/cockroachdb/cockroach/commits/bf01372d7ca0f2e6ad6dfa107d679182aee173dd):

```
=== RUN TestChangefeedProtectedTimestampUpdateForMultipleTables
test_log_scope.go:172: test logs captured to: outputs.zip/logTestChangefeedProtectedTimestampUpdateForMultipleTables4238522451
test_log_scope.go:82: use -show-logs to present logs inline
protected_timestamps_test.go:1142: -- test log scope end --
test logs left over in: outputs.zip/logTestChangefeedProtectedTimestampUpdateForMultipleTables4238522451
--- FAIL: TestChangefeedProtectedTimestampUpdateForMultipleTables (1.72s)
=== RUN TestChangefeedProtectedTimestampUpdateForMultipleTables/kafka
helpers_test.go:1777: making server as system tenant
helpers_test.go:1892: making kafka feed factory
testfeed_test.go:342: creating external connection
testfeed_test.go:345: ran create external connection
protected_timestamps_test.go:1080: error scanning '&{ 0x37c1bbae5400}': sql: no rows in result set
--- FAIL: TestChangefeedProtectedTimestampUpdateForMultipleTables/kafka (1.71s)
```

Parameters:
- attempt=1
- run=2
- shard=9
Help

See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)

/cc @cockroachlabs/cdc

[Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/bazci/githubpost/issues)

Jira issue: CRDB-67709

Start with ccl/changefeedccl.TestChangefeedProtectedTimestampUpdateForMultipleTables in protected_timestamps_test.go, especially the scan at line 1080 and the test log around line 1142. Run the targeted test with the kafka subtest and inspect the linked invocation logs. Done means identifying the cause of the missing row and making the test pass reliably.

Written by the indexing model from the issue text.