Feature/firestore optimistic locking #188

[mehdi0933]

Description

This PR addresses issue #188 by adding optimistic locking support to the Firestore sample application.

Changes

• Added the @Version annotation to the User entity in the Firestore sample app.
• Implemented getter and setter methods for the version field.
• Updated equals(), hashCode(), and toString() methods in the User class to include the version field for consistency.
• (Optional) Included minor adjustments to Datastore mapping properties to ensure project-wide consistency.

Motivation

Optimistic locking is a critical feature for handling concurrent updates in Firestore. By adding this to the sample app, we provide a clear example for users on how to prevent data overwrites using Spring Data Cloud Firestore.

Testing

• Verified that the project compiles successfully using ./mvnw clean compile.
• Confirmed that the User entity correctly maps the version field.

Fixes #188

See
also CONTRIBUTING.md
.