When sending facets in a search request, there is logic that first checks
whether FACET_FILTER_NODES exist. If none exist, we default to using whatever
was persisted in the URL. The issue was that this logic was not being duplicated
for persisting facets in the URL. If facets were applied from the URL on a search
run on page load, for example, we would try to persist facets using the FACET_FILTER_NODE
state on page load, which would be no filter nodes existing. Defaulting this to whatever
is persisted in the URL fixes the issue.

J=SLAP-1377
TEST=manual,auto

saw that I can double refresh the page with facets applied from the url, and also
that the back and forwards buttons work for facets

added a additional refresh and forward nav actions to the facetsonload acceptance test to
test double refreshing and forward naving with facets from the URL
added a new facetsonload.html for this test, with the only difference being
 searchOnChange: true for facets (which is the default as well as more common config setting)