[midPoint-git] [Evolveum/midpoint] 6a6dd4: Fix "no sync policy" treatment in LiveSync

[mederly]

  Branch: refs/heads/master
  Home:   https://github.com/Evolveum/midpoint
  Commit: 6a6dd40931345eefe47610ea698a64e7c66aaa41
      https://github.com/Evolveum/midpoint/commit/6a6dd40931345eefe47610ea698a64e7c66aaa41
  Author: Pavol Mederly <mederly at evolveum.com>
  Date:   2020-03-10 (Tue, 10 Mar 2020)

  Changed paths:
    M model/model-intest/src/test/java/com/evolveum/midpoint/model/intest/sync/TestLiveSyncTaskMechanics.java
    A model/model-intest/src/test/resources/sync/resource-dummy-no-policy.xml
    A model/model-intest/src/test/resources/sync/task-no-policy.xml
    M provisioning/provisioning-impl/src/main/java/com/evolveum/midpoint/provisioning/impl/sync/ChangeProcessor.java
    M provisioning/provisioning-impl/src/test/java/com/evolveum/midpoint/provisioning/impl/opendj/TestSynchronization.java
    M repo/repo-test-util/src/main/java/com/evolveum/midpoint/test/AbstractIntegrationTest.java
    M testing/story/src/test/java/com/evolveum/midpoint/testing/story/TestThresholdsLiveSyncFull.java
    M testing/story/src/test/java/com/evolveum/midpoint/testing/story/TestThresholdsLiveSyncSimulate.java

  Log Message:
  -----------
  Fix "no sync policy" treatment in LiveSync

Processing of such resource objects was originally considered to be
erroneous, so live sync task stopped when they were encountered.
But, in fact, these should be simply ignored.

So we added "not applicable" to the list of accepted operation result
statuses.

This resolves MID-5999.

Cherry-picked and adapted from 3e4e0be754503f5041f3575e41cc4f84a8446fb3.