Auto Resolution of DBRM Table Locks When Orphaned

cpimport creates table locks when inserting data into a columnstore table, however during a network failure in a cluster, or unforseen circumstance/hardware issue, its possible for the cpimport PID to be killed and gone, but the table lock still exist in viewtablelock.

The current workaround is to restart columnstore, during which loadbrm/rollback resolution resolves and frees the locks but the desire is for once the hardware issue is resolved, for these locks to auto resolve themselves. This will increase durability of the product and require less manual intervention to get back online.