Add a database transaction to the Output Manager Service when encumbering a received output

[philipr-za]

We have seen some occurence of an intermittent bug where if the direct and propagated transaction messages arrive at a receiver in rapid succession we can have clashes in the Output Manager database because receiving a transaction requires multiple database operations. When they operations are interleaved and cause an error it breaks the inbound transaction.

The operations in the transaction and output manager services for receiving a transaction should be encapsulated in a database transaction somehow to be completely atomic to avoid this.

[hansieodendaal]

Closed by:

• feat: optimize transaction service queries #4775
• feat: add sql transactions to encumbering queries #4716
• feat: improve txo validation logic #4689
• feat: wallet optimize output manager db operations #4663