ISPN-4693 Initial submission of handling for orphaned transactions.

Based off of production settings, I needed to iterate over both maps, since there are conditions where a local transaction can be orphaned as well.  

I'm wondering if instead of a rollback command, we directly grab the lock container and release the locks that way (and removing the transactions from the table via the existing methods).  I don't see how any exception can occur before the lock interceptors, but I'm not as familiar with the 7.0 code. 
...like the above.  This seems to be optimal for us per internal testing.