Fix missing break in tovmsspec.

When encountering a question mark in a filespec being converted
from Unix to VMS format, we were inadvertently adding an escaped
space because of a missing break in a switch.

(cherry picked from commit 774e463)

Author: craigberry

ext/VMS-Filespec/t/filespec.t

@@ -137,6 +137,7 @@ foo-bar-0^.01/	vmsify [.foo-bar-0_01] [.foo-bar-0^.01]
 +foo.tmp	vmsify ^+foo.tmp ^
 ../foo\ \ bar/	vmsify [-.foo^_^_bar] ^
 ./foo.tmp	vmsify []foo.tmp ^
+x/r*???????	vmsify [.x]r*??????? ^
 
 # Fileifying directory specs
 __down_:[__the_.__garden_.__path_]     fileify __down_:[__the_.__garden_]__path_.dir;1 ^

vms/vms.c

@@ -8731,6 +8731,7 @@ int_tovmsspec(const char *path, char *rslt, int dir_flag, int * utf8_flag)
 	else
 	  *(cp1++) = '?';
 	cp2++;
+	break;
     case ' ':
 	if (cp2 >= path && (cp2 == path || *(cp2-1) != '^')) /* not previously escaped */
 	    *(cp1)++ = '^';