[Experimental] - Integration tests refactor

any particular reason to use separate itests over just having itests named bundles in tests ? 
I guess being able to do "cd itests; mvn test"  is nice, but the other way "cd tests; mvn test -P noit" could work too *and* it would be easier to share cross dependencies. (since I assume if tests and itests are separate tests has zero dependencies to itests, but the other way around is okey)