Remove the should_fail/should_pass separation in E2E tests

[AlicanC]

Our E2E test suite separates tests into two directories: should_fail and should_pass. IIRC we were using these directories to determine what to expect, but we now do that with test.tomls and it doesn't really matter which directory a test sits in.

My suggestion is that we should not organize tests in this way. If you are working on a feature, all tests, failing or not, should be in the same directory.

So now it looks like:

test/src/e2e_vm_tests/test_programs/should_pass/passing_test_for_feature_a
test/src/e2e_vm_tests/test_programs/should_fail/failing_test_for_feature_a

And my suggestion is:

test/src/e2e_vm_tests/test_programs/feature_a/passing_test
test/src/e2e_vm_tests/test_programs/feature_a/failing_test

[otrho]

I considered this when introducing the test.toml testing, but it would've been too big a diff to do it then. But I agree, we really don't need to organise based on the test type, but rather what it is actually testing.