MINOR: fix places where IDE interprets ?> as end of PHP file

Not sure if this annoys others (or if your particular IDE does it in each of these places), but some editors interpret ?> in some locations as the end of the PHP file and it royally messes up syntax highlighting / formatting for the rest of the file after the ?> appears.  This simply breaks the strings that contain ?> so that the IDE will not interpret it as the end of the file.

I found all places in framework that had ?> (excluding thirdparty folders) and then replaced those that my IDE (vim) had problems with.  Others (like the ones in a <<EOF or comment block) did not cause formatting issues, so I didn't modify those.