Ensure thread safety for query listener collection on native driver

[kpgalligan]

The query listener collection is potentially accessed from multiple threads and needs to be thread safe. That is very likely the cause of: #4376

It is difficult to say for certain if that is the cause, as race condition issues don't generally produce obvious or repeatable crashes, but if you take the locks out of this PR and run the test, it'll crash hard.

For workaround in the issue, I'll comment on that in the issue in more detail. Summary, though, unless all access was in the same thread, it's still possible to have race conditions, and it looks like there are multiple threads still.

Presumably this has been an issue since this change: https://github.com/cashapp/sqldelight/pull/4148/files#diff-18eaa5efaf87c02833bc443af34a18778468fbe7e35dc9de4f01c61277593ce6R139

This is a pretty big runtime issue, so we should get a fix out, but again, it's hard to say for sure this fixes the originally observed behavior, so we'll really need to have it published and watch what happens.

[kpgalligan]

This collection was also changed in the PR that removed the old memory model.

https://github.com/cashapp/sqldelight/blob/kgalligan/2023-08-25/listener-concurrency/drivers/native-driver/src/nativeMain/kotlin/app/cash/sqldelight/driver/native/NativeSqlDatabase.kt#L346

Unlike the listeners, the statement cache should be OK as the connections are owned by threads. I wouldn't say I love having a regular mutable map here, but it should be OK, and unnecessary locking should be avoided.