Modify module to support optimistic locking

Overview:
In optimistic locking testing against the CP team's scratch environment, saving a record in the quickmarc editor generates a 500 response from the server. This error can be traced to mod-inventory throwing a 409 conflict. This is because mod-quickmarc isn't giving the version field a value.

This is blocked by MODSOURMAN-566 since the error is currently not reproducible. My theory is that the 566 is hiding it.

Steps to Reproduce:

1. In https://core-platform.ci.folio.org/ edit a holdings record in quickmarc.
2. Save the record. A 500 error is visible in dev tools. mod-quickmarc logs don't provide error details.
3. Open the logs from mod-inventory in rancher here
4. Look for the attempted update. See example from logs below.

Expected Results:
Edit should succeed.
Actual Results:
Logs from mod-inventory:

11:54:11 [] [] [] [] ERROR stanceUpdateDelegate Error updating Instance - { "message": "Cannot update record b69dddcd-6f08-44a0-b3bb-015a3f13f9e4 because it has been changed (optimistic locking): Stored _version is 2, _version of request is <NULL>", "severity": "ERROR", "code": "23F09", "where": "PL/pgSQL function instance_set_ol_version() line 8 at RAISE", "file": "pl_exec.c", "line": "3841", "routine": "exec_stmt_raise", "schema": "diku_mod_inventory_storage", "table": "instance" }, status code 409

Additional Information:
This error is not currently reproducible and is blocked/hidden by MODSOURMAN-566.  I'm assigning it to myself to keep track of it.
Interested parties:
jakub, Hanna_Hulevich@epam.com, kgambrell, abreaux