Update existing job instances instead of inserting/replacing in Data Index #2177
Description
Due to the current implementation of job indexing in the Data Index, when a job event is processed, full insert/replace operation on the job entity is performed. This approach overwrites all existing field values in the database, including fields that may have been set or updated. The issue is that this leads inconsistency when existing job entities are updated, as any previously stored values are replaced with the values from the incoming event, regardless of whether those values are more current or accurate than what's already persisted.