Drop the runtime.patchConfig flag as NRI is on on both runtimes

I guess we are reaching the point where the `runtime.patchConfig` is becoming somewhat dead assuming NRI is enabled by default on both container runtimes for a quite a while. I think it must be very old (unsupported) version of the runtime that would require NRI to be turned on manually.

Should we drop the flag? Any concerns @klihub @kad ?

The issue identifies runtime.patchConfig as the entry point, but names no files or tests. Locate its definition and all runtime-specific uses first; done means the obsolete flag is removed without requiring manual NRI enablement on either supported container runtime.

Written by the indexing model from the issue text.