1. Use session-level instead of transaction-level LockService implementations. Session-level locks get automatically released if the database connection drops. This way, there won't be any garbage in the DATABASECHANGELOGLOCK table and it will always be in a valid state.

2. I would exclude the data of the DATABASECHANGELOGLOCK table from your dump entirely, since its data represents the processes of your production state and has nothing to do with the dev state.