Before this fix, we were doing log.Info().Err(err), which emits a
one-line log that is both info and error:

{"level":"info","error":"resource not found","namespace":"demo2","time":"2023-07-24T15:23:17+02:00","message":"no pre-existing PolicyReport, will create one at the end of the scan"}

Signed-off-by: Víctor Cuadrado Juan <[email protected]>

We are looking for namespaced resources, clusterwide resources get
checked in getClusterWideResourcesForPolicies()

Signed-off-by: Víctor Cuadrado Juan <[email protected]>

When policies are configured with a spec.rules GVK,
if resource doesn't exist because it has an incorrect GVK,
or if because it is a CRD that we don't know about,
emit warning and skip resource from scan.

The same for when policies are configured with a spec.rules GVK that the
audit-scanner lacks permissions for,
emit warning and skip resource from scan.

Signed-off-by: Víctor Cuadrado Juan <[email protected]>

Signed-off-by: Víctor Cuadrado Juan <[email protected]>

Signed-off-by: Víctor Cuadrado Juan <[email protected]>

Needed, as we need a client when we do `fetcher.isNamespacedResource()`.

Signed-off-by: Víctor Cuadrado Juan <[email protected]>

Signed-off-by: Víctor Cuadrado Juan <[email protected]>

Signed-off-by: Víctor Cuadrado Juan <[email protected]>

Add a test that checks that we don't error nor panic when trying to
filter resources that are forbidden (because the client lacks
permissions, normally because the ServiceAccount is insufficient).

Signed-off-by: Víctor Cuadrado Juan <[email protected]>

Signed-off-by: Víctor Cuadrado Juan <[email protected]>