Add metric(s) for KSM errors

[rexagod]

          Seconding Damien, I'm not for panicking the binary since we expect a [reload](https://github.com/kubernetes/kube-state-metrics/blob/f8aa7d9bb9d8e29876e19f4859391a54a7e61d63/internal/wrapper.go#L61-L62) on configuration change, and then a log (or metric) indicating an issue with the given configuration. Crashing the binary goes against the controller-esque behavior and allows anyone (with access) to crash a running instance simply by supplying a bad config.

That said I can definitely see a pain point here and maybe we should add a new metrics to report any kind of misconfiguration so that it would be more visible to cluster admin when kube-state-metrics is misconfigured.

+1 all the way. I'll add one.

Originally posted by @rexagod in #2434 (comment)

[rexagod]

Not sure how this never came up until now, this seems like a good addition addition for telemetry.

[logicalhan]

/triage accepted
/assign @rexagod