We do not want to create a new RecipeView every time we need to refresh
the recipes; this leads to leaking RecipeView objects, which have
subscribed event listeners.  This isn't the most elegant solution, but
it gets the job done.

Also add a method to clear the contents of the RefreshView between times
it is displayed.  Recreating the RefreshView every time is a small
memory leak.

Recreating the StashView every time we want to refresh the stash is a
memory leak, and makes Procurement lag while it rebuilds the stash.  As
an added bonus, now the last-selected stash tab remains selected when
revisiting the stash.

The onStashLoaded events were not being fired when loading character
inventories, so 1) there was no loading message for these "tabs" when
refreshing [used] tabs, and 2) the appropriate actions to take when
reloading tabs were not happening.