add a new known issue to the Troubleshooting doc section

When working with Camel-k on a local Kubernetes environment (eg. Minikube) I noticed the Operator get fails to build and deploy a kit. The error msg I could see inspecting the Operator's log is:

camel-k-operator-76fc5f56cb-cp8rk camel-k-operator {"level":"error","ts":1674582259.5047536,"logger":"camel-k.controller.build","msg":"Build kit-cf81hpsg8lv4vh3c8sqg failed: could not pull base image image 10.100.48.235/knativetutorial/camel-k-kit-cf7f88kg8lv99n0ojfp0@sha256:b318b4f92fef1b91b8873777935e2f65cef6724e65ca4e3d0d9d19aede5dc18d: GET http://10.100.48.235/v2/knativetutorial/camel-k-kit-cf7f88kg8lv99n0ojfp0/manifests/sha256:b318b4f92fef1b91b8873777935e2f65cef6724e65ca4e3d0d9d19aede5dc18d: MANIFEST_UNKNOWN: manifest unknown; map[Name:knativetutorial/camel-k-kit-cf7f88kg8lv99n0ojfp0 Revision:sha256:b318b4f92fef1b91b8873777935e2f65cef6724e65ca4e3d0d9d19aede5dc18d]","request-namespace":"knativetutorial","request-name":"kit-cf81hpsg8lv4vh3c8sqg","api-version":"camel.apache.org/v1","kind":"Build","ns":"knativetutorial","name":"kit-cf81hpsg8lv4vh3c8sqg","stacktrace":"github.com/apache/camel-k/pkg/controller/build.(*monitorRoutineAction).updateBuildStatus\n\tgithub.com/apache/camel-k/pkg/controller/build/monitor_routine.go:197\ngithub.com/apache/camel-k/pkg/controller/build.(*monitorRoutineAction).runBuild\n\tgithub.com/apache/camel-k/pkg/controller/build/monitor_routine.go:181"}
camel-k-operator-76fc5f56cb-cp8rk camel-k-operator {"level":"info","ts":1674582259.532116,"logger":"camel-k.controller.build","msg":"state transition","request-namespace":"knativetutorial","request-name":"kit-cf81hpsg8lv4vh3c8sqg","api-version":"camel.apache.org/v1","kind":"Build","ns":"knativetutorial","name":"kit-cf81hpsg8lv4vh3c8sqg","phase-from":"Running","phase-to":"Failed"}

Apparently, during the building kit phase, the Operator fails to pull the image from the internal Image Registry. Maybe due to some dangling image.

@christophd shared with me a workaround to solve this issue:

remove all integration kits kubectl delete ik --all in the Camel K operator namespace.
remove all dangling images again docker rmi $(docker images -f "dangling=true" -q).
removed all integrations kamel delete --all in failed state (maybe optional)

I think it worth to add this workaround to the https://camel.apache.org/camel-k/1.11.x/troubleshooting/known-issues.html page

apache / camel-k

add a new known issue to the Troubleshooting doc section #4007