[Proposal] Deploy CRI-RM as DaemonSet instead of systemd.unit

[ppalucki]

Not sure is it possible, to have fully functional CRI-RM running as privileged container with access to nessesary hosts path and there can be some issues unix socket connectivity between host kubelet and CRI-resource-manager running as pod.

Pros:

• simplified deployment
• access to logs
• "cloud native"

Cons:

• Egg and chicken problem when installation fails to restart kubelet
• Risk of limited host access by CRI-resource-manager for "future/unknown" policies

Note: not new idea, closed PR in cri-resource-manager can be found here: intel/cri-resource-manager#55