Work around bug in issue #936

The regexp engine used in aarch64 builds has a bug where /x[^x]*?$/
will not match when /x[^x]*$/ will, which causes issues with lockfiles.

Simply removing the ? (which in this case should not change the
results) resolves it.

Other cases of *?$ in regexps should be investigated to ensure this
is the only workaround (this is the only case of an inverted alternative
followed by *?$ I can find though).

exec/binkit.js

@@ -99,7 +99,7 @@ FREQIT.add_file = function(filename, bp, cfg)
 function lock_flow(file)
 {
 	var ret = {
-		bsy:new File(file.replace(/\.[^\.]*?$/, '.bsy')),
+		bsy:new File(file.replace(/\.[^\.]*$/, '.bsy')),
 	};
 
 	// Takes ownership of a lockfile if it's more than six hours old.