panopoly_search_update_7005 fires too early

In anticipation of some users of our Panopoly-based distro improperly trying to update from an old version with a really old Panopoly core (pre-1.14) up to the latest 1.37 in a single step (vs. going to Panopoly 1.27 and then on to 1.37 in a second update), I came across a DB update issue - panopoly_search_update_7005 was trying to execute before search_api_update_7118(). It was returning SQL errors about the search_api_item_string_id table not being found.

The attached patch cleared that problem up.