Remove shared home lock

The shared home lock is the only part of Bitbucket Data Center that requires the NFS lock service to work, and the possible misconfigurations that it can catch are so low probability that it's not really worth the trouble it causes. Remove it.

Original issue:

Problem

When the shared and/or home folder is on an NFS mount, but lockd is not running or the port that the daemon is running on is filtered, file creation/modification/etc works as expected, but file locks cannot be made. This will prevent Bitbucket Server or Data Center from starting up, producing the symptoms outlined in the following KB article: Bitbucket Data Center node hangs on startup - Initializing spring context

Steps to reproduce

1. Move the shared folder or the entire Bitbucket home of an existing instance to a NFS storage, mount it according to the requirements.
2. Test that the instance starts up correctly with all the NFS daemons running
3. Shut down the instance
4. Stop the lockd process or deny the port that the daemon is running on (identify by portmap -p)
5. Start the instance, observe that it's stuck on startup as mentioned in the above KB article

Suggestion

It would be useful to have a separate thread that is creating a lock and failing to do so in a pre-defined period of time, the thread would time out. Currently the startup may be stuck forever, without any meaningful error message.