Log: plugins warn that enricher is not initialized

**Describe the bug**

In Retina Advanced Mode, warnings might appear as "retina enricher is not initialized." This happens when using Hubble, which already provides pod-level info, making the enricher not initialized. This is expected behavior in Advanced Mode with Hubble and does not indicate a fatal error, but ideally, it shouldn't log this complaint from upstream Retina:

`level=info caller=packetparser/packetparser_linux.go:192 msg="setting up enricher since pod level is enabled"`
`level=warn caller=packetparser/packetparser_linux.go:197 msg="retina enricher is not initialized"`
`level=warn caller=dns/dns_linux.go:73 msg="retina enricher is not initialized"`
`level=info caller=dropreason/dropreason_linux.go:252 msg="setting up enricher since pod level is enabled"`
`level=warn caller=dropreason/dropreason_linux.go:257 msg="retina enricher is not initialized"`

Example: https://github.com/microsoft/retina/blob/fae9250faf8f9bc7df9a346d225b8880d3ba26d6/pkg/plugin/dns/dns_linux.go#L67