Query Work Bench should support implicit transactions

Splitting from MB-40206, since there are two aspects to transaction support. The first is supporting multiple statements in a transaction, which is already done.

This issue relates to supporting a single statement (usually an UPDATE) as an implicit transaction. The UI is pretty cluttered as is, so we need to find some way to let the user say, "execute this next statement should be an implicit transaction".