Return strict-decode errors in `NodePrepareResources()` as `permanentError`

[jgehrcke]

The strict decoding error introduced in #587 is actually a permanent error. Even if the kubelet doesn't understand that yet, we should return that to the kubelet already.

This relates to the discussion we had in #375, in particular

We can slowly add them in preparation for the kubelet even supporting them at all.

Having the notion in our driver is there to future proof us once the kubelet does support this / not keep us looping in the driver unnecessarily on a permanent error

[klueska]

Yes. I had actually thought of this, but forgot about it during the review...

[jgehrcke]

I had actually thought of this, but forgot about it during the review...

That's good :) The tiny detour here for me is worth it. Working on that patch now.

[nojnhuh]

FYI implementing this in kubelet is being tracked in kubernetes/enhancements#5322. I've been dragging my feet getting that KEP going but this is a great sign that that would be useful!

[jgehrcke]

@nojnhuh thanks -- let me know if I can help with driving that forward (that might be great project for me to get my feet wet and learn about the process).