Perf: Optimize SQL transaction commits in binlog replication applier

[fulghum]

The binlog replication applier process is responsible for applying the replicated updates from a MySQL source to the Dolt replica. Previously, when committing SQL transactions after applying a change, the applier would attempt to commit on all known databases. This worked when the number of databases was small, but when the server is handling hundreds of databases, it adds noticeable and unnecessary delay. This change switches to use the dirty tracking data of the session to more efficiently commit to only the databases that have had changes applied.

Performance Comparison

The old SQL transaction commit logic scaled exponentially, while the new logic scales linearly.

Num Databases	Code Path	Replication Time (s)
100	Old	11.02
300	Old	144.34
500	Old	633.44
100	New	6.79
300	New	20.51
500	New	36.04

[coffeegoddd]

@fulghum DOLT

comparing_percentages
100.000000 to 100.000000

version	result	total
4c4e9bc	ok	5937457

version	total_tests
4c4e9bc	5937457

correctness_percentage
100.0

[jycor]

LGTM