Allow a PullRequestElement to have both a ForeignTable and Range

The IMQS backend gracefully handles this, by building up a JOIN
statement based on the table relationships. The original constraint
makes sense, but it's just not practical.