Unique lock key based on database and table name

[pandeybk]

If multiple instances of Vault deployment trying to use the same MySQL DB endpoint, the first deployment will hold lock forever and others deployment will fail to insert record in the lock table, which is causing the following issue,

URL: GET https://127.0.0.1:8200/v1/sys/leader
Code: 500. Errors:

* SQL: no rows in result set

The unique lock key per vault deployment will resolve this problem.

[hashicorp-cla]

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

---

1 out of 2 committers have signed the CLA.

• pandeybk
• Balkrishna Pandey

---

Balkrishna Pandey seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA. If you already have a GitHub account, please add the email address used for this commit to your account.

_{Have you signed the CLA already but the status is still pending? Recheck it.}