VAAPI: Don't use swfilter for large surfaces - fallback to vaapi render

This stops using of sse copy routines for large surfaces. It introduces a fallback to the swrender - cause the statemachine wants a correctly setup m_pp after that method, if we don't care for this AddPicture will segfault.

Open for more input, e.g. better error handling.
At the caller you don't know what overload will be called. I have seen too many cases where this does harm and the rule is very simple: just avoid it in general.