Work around Intel's failings with buffer_storage

[Sonicadvance1]

No description provided.

[delroth]

OMGz, working around Intel driver failing? Page @neobrain.

But more seriously, LGTM. I'm curious as to whether that's a Dolphin issue or an Intel issue - at this point in time, our buffer storage code has been fairly well tested, so I'd be inclined to say it's Intel's fault...

[Sonicadvance1]

Very much Intel's fault, it shouldn't fail on this buffer type.

[delroth]

Well, it could be that we're out of spec and that it's only showing now. That wouldn't be the first time this happens (for example, some of our GLES issues where very much this). Without more time spent debugging this I wouldn't 100% assume it's Intel's fault - but it's very, very likely.

[TurboK234]

I reported this issue on Intel Graphics forums at https://communities.intel.com/thread/54819 , and they responded already, and the apparently have replicated the issue and are working on it. Good news!
I still find this workaround needed, since next Intel drivers might be some months from now. And this fix is driver version specific, isn't it?

[magcius]

Having this nice and contained inside DriverDetails makes this fine to me. Workarounds are only terrible if they have shitty code quality.

LGTM.