Currently the nmstate configs are added to the InfraEnv when the InfraEnv is registered with assisted-service. Now, the nmstate configs could appear after the InfraEnv is registered. We need to refactor the client to poll the file system to detect when the nmstate configs becomes available and then update the InfraEnv with the new configuration.

Proposed flow:

• The client polls for nmstate configs in the file system
• Once nmstate configs are detected, the client queries the assisted-service REST-API to check if an InfraEnv has been registered
  • If yes, the nmstate configs are added to the InfraEnv through the assisted-service REST-API. Care must be taken so that no duplicates are added through the REST-API.
  • If no,  the client sleeps and retries above