Comment 2 for bug 1891960

Here's a branch that provides this behavior: user/sandbergja/lp1891960_sticky_ou_patron_search

Note that the Angularjs patron search org field is storing its settings in the browser, rather than the database, so I didn't attempt any migration of those values. Staff members will have to set their desired search org separately in Angular (which shouldn't be much of a hassle).

Testing notes from the commit message:
1) Find a title in the staff catalog.
2) Click Place Hold.
3) Search for a Patron.
4) Notice that the search org is initially
your root org (Consortium-level).
5) Select a different value.
6) Leave and come back to this screen. Note
that the value you selected remains.
7) Perform a search to make sure that the
search is limited to the org you selected.
8) Click the Clear button. Note that the
value you selected still remains.
9) Perform another search to make sure that the
search is limited to the org you selected.