Issue Summary

Objects created manually are linked to the first import run after their creation as their source, and the missing objects configuration is picking such objects

Steps to Reproduce

1. Create an object manually from the UI for an Object Type
2. Run any import that contains mapping for the OT with the missing objects configuration set to Update/Remove with a threshold of 0. This import is now mapped as the source for this manually created object.
3. On running the import again, the object is now marked as missing and updated/removed as per the configuration.

Expected Results

The manually created object should not have been updated/deleted from the missing objects configuration

Actual Results

The manually created object is marked as missing for the import source and is updated. This happens because we create entries in the obj_source_mapping for all the objects that don't have a mapping. This was done as part of the fix when missing objects were not working at the start after the migration. The fix could be to run this mapping only once for every OT.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available