Localization of WPeC user javascript variables is now more explicit
The loop that was taking the localized admin js vars out of the localization structure and putting them into the window content has been replaced by explicit assignments. Although it is a little more code than the prior loop it should now be easier to see what is happening.
For localized js vars added after 3.8.14 three utility functions have been provided to access localized vars
 wpsc_var_get ( name )
 wpsc_var_set ( name, value )
 wpsc_var_isset ( name, value )

This PR also contains the user side of the audit required to close issue #1110
removed term 'legacy' from description
Sadly, we need to hold off on using HTML5 number inputs for now.  The reason here is that at this point in time, the number input chokes on commas.  So if you have values in the thousands (or even decimals, for countries that use commas as decimals), it chokes.  It simply doesn't show the value.
Merge remote-tracking branch 'upstream/master' into pr-issue-1110-legacy-js-vars-explicit-into-user-js

Conflicts:
	wpsc-core/js/wp-e-commerce.js
Remove , as it is unused.  This logic was moved to wpsc_determine_variation_price().
Merge pull request #1128 from JeffPyeBrook/pr-issue-1110-legacy-js-vars-explicit-into-user-js

Localization of WPeC user javascript variables is now more explicit
Merge changes to wp-e-commerce.js
Merge remote-tracking branch 'upstream/master' into pr-issue-1087-localization-geo-and-ajax-updates

Conflicts:
	wpsc-core/js/wp-e-commerce.js