New support for one or more search_location_setting_set values in the INI

-- Rather than constantly having to repeat the location values on every
search you want to run, you can now just add a new
search_location_setting_set section in your INI file that defines all
the possible location values for each of the different possible types.
That set of values in search_location_setting_set will then be
automatically applied to each job site you have listed to search.

Example INI section:
[search_location_setting_set]
name="Search Locations"

[search_location_setting_set.Seattle]name="Seattle"
location-city="Seattle"
location-city-comma-statecode="seattle, wa"
location-city-comma-statecode-underscores-and-dashes="seattle__2c-wa"
location-city-comma-state="seattle, washington"
location-city-comma-state-country="seattle, washington, united states"
location-city-comma-state-country-no-commas="seattle washington united
states"

-- Note:  you can still specify a location="blah" value on a per search
basis.  Jobs_scooper will use that location value for that search
instead of using any location setting sets.

- Results text now separates out the counts for jobs retrieved from the
user's inputted CSV files.  This makes it clearer to see what jobs were
actually pulled and or updated with this run.

- set a C__STR_USER_AGENT__ constant value directly in jobs_scooper to
be used in the XML and other calls

- renamed consts JOBSITE_BASE_*_FLAGS to C__JOB_BASETYPE_*_FLAGS so
that they are consistent with the other flags they are typically OR'd
against

- set separate ScooperLib value, $GLOBALS['OPTS']['VERBOSE_API_CALLS'],
so that CURL calls do not spew out the verbose call information