Shared: improve join order in filterByLocation

It's better to join with the range expression first since that will only
multiply tuple counts by the number of lines in an average source/sink.
Joining with `restrictAlertsToStartLine` first would multiply tuple
counts by the number of sources/sinks in a given file.

shared/util/codeql/util/AlertFiltering.qll

@@ -98,7 +98,7 @@ module AlertFilteringImpl<LocationSig Location> {
       exists(int locStartLine, int locEndLine |
         location.hasLocationInfo(filePath, locStartLine, _, locEndLine, _)
       |
-        restrictAlertsToStartLine(filePath, [locStartLine .. locEndLine])
+        restrictAlertsToStartLine(pragma[only_bind_into](filePath), [locStartLine .. locEndLine])
       )
     )
     or