With the recent changes done on DDLLockManager to use LockManager instead of self-manage DDL locks, we have lost the ability to know which DDL operation is holding the given resource when a LockTimeout exception is thrown during a DDL lock acquisition.

The aim of this ticket is to investigate and implement a way of getting that information and print it out once a LockTimeout raises, as well as the old DDLLockManager did here.