Make imports idempotent

[rranjan3]

PULL DESCRIPTION

Make imports idempotent. Since the registration is a multi-stage action

• allow an import in second iteration if the failure happened midway in the 1st
• report duplicate only if the host registration as well as instance creation is already done
• no deep compare to allow update of fields, if instance already created

Impact Analysis

Info	Please fill out this column
Root Cause	Specifically for bugs, empty in case of no variants
Jira ticket	ITEP-25036

CODE MAINTAINABILITY

• Added required new tests relevant to the changes and the URL has been included
• Updated Documentation as relevant to the changes
• PR change contains code related to security
• PR introduces changes that break compatibility with other modules/services (If YES, please provide description)

Code must act as a teacher for future developers

[rranjan3]

1.) Faulty os profile is deliberately induced
2.) Import attempted which fails with no data in EIM persisted(Pre-validation ensures, even host registration is not done if invalid input)
3.) profile corrected & import reattempted
4.) Import succeeds by registering host & then creating instance.

[pierventre]

1.) Faulty os profile is deliberately induced 2.) Import attempted which fails with only host registration 3.) profile corrected & import reattempted 4.) Import succeeds by creating instance.

do we have unit tests emulating a similar scenario?

[rranjan3]

1.) Faulty os profile is deliberately induced 2.) Import attempted which fails with only host registration 3.) profile corrected & import reattempted 4.) Import succeeds by creating instance.

do we have unit tests emulating a similar scenario?

Need to add e2e test.

[pierventre]

lgtm

[pierventre]

lgtm - make sure it is visible in the README the overriding behavior between global vs user input