[Backend development] Implement: prevent conflict once detected. Enable "failOnConflict"

Requirement

• #2 [Backend development] Implement: prevent conflict once detected. Enable "failOnConflict"
• Teams follows documentation available: https://github.com/folio-org/raml-module-builder#optimistic-locking
• Dependency version updates required?
• Error handling
  • Error codes
  • Error messaging

Acceptance criteria

Given I click Save on a record
When an indicator displays that another person is editing the same record
Then ???

Given I take an action on a record
When an indicator displays that another person is editing the same record
Then ???

Given I take an action on a record
When an indicator displays that a system is editing the same record
Then ???

Given a system is updating a record
When another system is updating the same record
Then ???

Given an automated process is updating a record
When another automated system is updating the same record
Then

Given I take an action on a record OR edit a record
When an Optimistic locking error occurs
Then ???

Definition of done

• Implement Karate API tests
• Verify that key use cases are addressed
• [NOTE: POs should review below scenarios and edit based on workflows.]

Potential multiple users are editing the same record at the same time scenarios for testing

Potential scenarions for 1 user and system trying to act on the same record, either individual records or batch

Potential scenarios for Two automated processes acting on the same record