[bug 4.1] Updated BladeCompiler to handle a statement that comes immediately follo...

When Blade compiles statements using `createMatcher` and `createOpenMatcher`, it uses the dot operator to find the expression to use in `preg_replace`. However, this causes problems when one statement immediately follows another (see `testIncludesAreCompiled` in [the BladeCompiler tests](https://github.com/tshelburne/framework/blob/ca886d4cd3f12182ba65d537ccc6b55cffc15f39/tests/View/ViewBladeCompilerTest.php#LC262)). To avoid this, I updated the regex to stop when it hits either of the '@' or '<' characters, to handle statements that have yet to be parsed, as well as those that have already been compiled. 

This isn't an issue in 4.2 and beyond, but I've run into it a couple times in my project and I can't jump to 4.2 yet.