Don't emit Prune event for NoMatchError

[Liujingfang1]

The existing prune has a bug when handling the following case:

1. The inventory list contains a CR
2. The CRD is deleted from the cluster. Consequently the CR is also deleted from the cluster.
3. Then remove the configuration for the CR from the local directory
4. Apply the directory, since the CR is in the previously applied set and not in the current apply set. The CR should be pruned.
5. When getting the CR from the cluster, an error is get since no type is matched since the CRD is deleted.
6. It emits a PruneEvent with this error.

Since the CR doesn't exist in step 5, we actually don't need to trigger the deletion for it. Emitting the PruneEvent with an error doesn't make sense either. It only needs to remove the GKNN of the CR from the inventory list, which is already done by the current code.

This PR checks if the error from step 5 is a NoMatchError. It it is, continue to the next object.

[Liujingfang1]

/assign @seans3 @mortent

[mortent]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Liujingfang1, mortent

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [Liujingfang1,mortent]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment