NodeCondition on failing to run system pods

There are many cases when Node become broken when system pods are failing to run. For example:

- Image pull issues
- Init container failures
- Other Crash Loop Backoff cases

I think introducing a new Node Condition when any of the system namespace pods has failed will be very useful.

Seeking for feedback - are there ever cases when system pods are failing to run and node is not "degraded".

Also, may be a rule like this may be configurable to include additional namespaces to check.

No file, test, or entry point is named. Start by locating the Go code that reports node conditions and handles system-namespace pods, then review existing tests for failed image pulls, init containers, and crash loops. Done means the proposed condition and any namespace configuration behavior are specified, implemented, and covered by tests.

Written by the indexing model from the issue text.