anv: Create protected engine context when i915 supports vm control
What does this MR do and why?
When has_vm_control is supported it takes a different code path and creates one context per engine and in this code path we were not setting the protected context flag.