node-reaper to handle longer time node drain case

[figo]

Is this a BUG REPORT or FEATURE REQUEST?:
feature request

What happened:
Currently, when node drain timeout, node-reaper will mark the node uncordon, and then try to drain it again in next round (approx in next 10m )

for the node that has pod take long time to be evicted, it is possible that the same node can be under constant drain.

What you expected to happen:

set node drain timeout to 1hr or longer if possible.

How to reproduce it (as minimally and precisely as possible):
run the node-reaper with pod that take more than 10m to be evicted

Anything else we need to know?:
N/A

Environment:
N/A

• Kubernetes version:
  N/A

kubectl version -o yaml

Other debugging information (if applicable):

• relevant logs:

kubectl logs <governor-pod>

[eytan-avisror]

There is already a --drain-timeout flag that allows changing the default 600s, but it would be global to all namespaces.
In this case it seems we want a feature to be able to selectively change this for a specific namespace that might want more than 600s rather than changing it for everyone?