Try to avoid undefined table civicrm_setting when doing an upgrade from 3.x / 4.0.x -> 4.1

If we transfer a DB from live to test AND reset the config_backen, i.e. civi needs to rebuild the config, we'll get an ugly DB error throw since the 4.1 code is executing

Making a special case for upgrades to avoid this issue