fix(gc): Do not log 403 errors on deletecollection requests during GC

[astefanutti]

Fixes #1140.

Release Note

NONE

[nicolaferraro]

Did you have also a look at #1027? Seems another category of error to skip.

I've not found a k8s API to deal with unknown API, so I've added a util method

camel-k/pkg/util/kubernetes/errors.go

Line 25 in 0605fd1

return err != nil && strings.HasPrefix(err.Error(), "no matches for kind")

[astefanutti]

It seems to me #1027 is a different kind of error:

• The GC relies on the discovery API that has returned the CamelSource type, so I find it strange the delete operation fails with the no matches for kind error,
• I'm not sure the integration GC should actually enlist the CamelSource type for GC. I think it happens by accident as it happens the label selector matches the CamelSource owner, while it should probably not.

[nicolaferraro]

Yeah, I can see it's a strange error.
I'm moving that issue out of the milestone as it does not happen consistently.