We need this to support EF-150.

We should check the connection to ensure it supports transactions at launch time and not attempt to use them if it is standalone so as not to break local development scenarios. We can emit a warning about lack of transactions into the logs.

Other types of transactional support - e.g. System.Transactions and explicit EF transactions will be tackled in other (future) tickets.