fix(datastore): handle consistent azure native-ids

[browdues]

Problem:

After a destroy/re-apply cycle, some dependent resources fail to resolve references to their parent resources.

This affects cloud providers like Azure where native_id is deterministic (based on subscription/resource-group/name)

Fix:

1. Track whether KSUID was provided vs generated in storeResource
2. Only adopt discovered KSUID if incoming resource didn't already have one assigned
3. Check if incoming KSUID matches existing KSUID before returning early; only skip insert when BOTH data AND KSUID are identical