Owls 89909 - Fix for repeated introspection after a rolling restart of a MII domain because of image hash mismatch

[ankedia]

Owls 89909 - In some cases, when the domain is updated with an image that doesn't make any actual changes to the domain, it's considered as a no-op in modelInImage.sh, and the domain config parsed from the introspector log is null. However, the domain is rolled because the image name is different. In such cases, the image hash stored in the introspector config map is different from the actual image hash. The make-right cycle checks if the image hash stored in the config map matches the actual image hash when deciding whether a new introspector job needs to be created. This causes the introspector job to be created multiple times.

This change stores the new image hash in the packet and also patches the config map with the new hash when the introspection is a no-op. Integration test run at - https://build.weblogick8s.org:8443/job/weblogic-kubernetes-operator-kind-new/5389/