remove sanity check for existence of include which isn't always there

Assuming include is always there, it's a reasonable check to do in tests,
but it isn't and I don't think it matters enough to fail the test, so why
is it there?

(And here's another reminder that it's really not possible to determine if
a dir is a virtualenv without just using it)