Consider looking up for an ignore list when checking Pod volumes for service-mesh enabled environments

[Dentrax]

Is your feature request related to a problem? Please describe.
Descheduler doesn't work as expected in a service-meshed (istio) environment due to emptyDir local volumes.

Istio sidecar includes the following volumes:

- emptyDir:
    medium: Memory
  name: istio-envoy
- emptyDir: {}
  name: istio-data

That means, if you are using the Descheduler on a large service-mesh force-enabled clusters, it wouldn't take any effect, due to Pod sidecars that injected on runtime.

Almost all Descheduler instances across all clusters, throws the following error:

Pod fails the following checks" pod="ns/my-pod" checks="pod has local storage and descheduler is not configured with evictLocalStoragePods

Describe the solution you'd like
Pass additional options to IsPodWithLocalStorage for more control on how should behave.

In the configuration, I'd like to pass some ignore list:

1. to ignore by container name (i.e., istio-proxy)
2. to ignore by volume name

By doing so, the Descheduler will start work as expected on service-meshed environment.

Describe alternatives you've considered
Set evictLocalStoragePods to true. But its a bit risky to enable this on production because it will entirely ignore the volumes as expected. We'd not want this.

What version of descheduler are you using?

descheduler version: 0.28

Additional context
-