[LocalID] Concurrent submission of same localID issue

[mreyescdl]

When submitting multiple new objects with the same local ID concurrently, the following can occur:

• Different primary IDs can get bound to the same Local ID

This occurs due to the Local ID not being locked during the DB update.
A fix would be for either Ingest or the Local ID service to create a Zookeeper lock based on OWNER + LOCAL ID before the update and release after the update

[elopatin-uc3]

Local ID integration test can trigger this error. If local id exists previously, error is not triggered. Error can be triggered after the stage cleanup script runs on Fridays.