Proximity Adjustment rules can be used too broadly

[Mike Rylander]

The canonical use case for proximity adjustment is to use it broadly to effect the local proximity of items within a particular area, in a like manner, across many parts of the org tree. However, in cases where it is lightly used, or used with non-overlapping criteria columns, there are cases where the adjustment will spread beyond its intended range of influence.

The changes here create a much stricter and correct test for rule matching, which will end in the correct choice of rules in all cases.

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/miker/prox-adjust-fix

[Lebbeous Fogle-Weekley (lebbeous)]

This branch adds my signoff to Mike's two commits and a test in the third, which is good not only for its own sake but because it adds a more concrete expression of what's right behavior (and what proximity adjustment was formerly getting wrong).

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/collab/senator/prox-adjust-fix

[Mike Rylander (mrylander)]

Pushed to the appropriate branches. Thanks for the test and signoff, Lebbeous!