Introduce optimistic locking support via optional parameter last_commit_id on File Update API

What does this MR do?

Implements #32642 (closed): Introduce optimistic locking support via optional parameter last_commit_id in repository file update operation.

Does this MR meet the acceptance criteria?

• Changelog entry added, if necessary
• Documentation created/updated
• API support added
• Tests
  • Added for this feature/bug
  • All builds are passing
• Conform by the merge request performance guides
• Conform by the style guides
• Branch has no merge conflicts with master (if it does - rebase it please)
• Squashed related commits together

What are the relevant issue numbers?

Closes #32642 (closed)