API and command line option change: -reset_failed_jobs and -reset_all_jobs now work with -analyses_pattern

API change: Scheduler::schedule_workers_resync_if_necessary() and Scheduler::schedule_workers() now take an obligatory $list_of_analyses

balance_semaphores() returns the number of unsemaphored jobs, and the second sync() is only done if a nonzero number of semaphored jobs were unsemaphored

internal api cleanup: switched to more intuitive set_and_update_status/check_in_worker/check_in_job calls

removed rearrange() and throw() from AnalysisJobAdaptor by removing the unused CreateNewJob() method

cosmetic: added deprecated message to CreateNewJob() and some documentation to store_jobs_and_adjust_counters()

store_jobs_and_adjust_counters() now also deals with semaphore_count corrections. It is now the preferred job-creation interface.

bugfix: no hope for other DBD drivers to support detection of auto-incrementing fields => use our inernal fixed rule

bugfix: stop printing overflow-related debug output to STDOUT; interface with overflow adaptor simplified

drop fetch_all_by_from_analysis_id_and_branch_code() method and rely on AUTOLOADed BaseAdaptor's methods instead

(1) do not change SEMAPHORED jobs to READY and (2) support more flexibility in choosing which statuses to reset

bugfix: ENSCOMPARASW-132. When all dependent jobs (>1) fail to be created due to unique constraint, they now correctly update status to READY

bugfix: reset the tried jobs to retry_count=1 and untried ones to retry_count=0 when doing a bulk reset

bugfix: make sure longer input_id hashes are correctly fetched from analysis_data table in "param stack" mode

"parameter stack" implementation using two extra fields in job table. Accu content intended for any job_id has preference over Input_id content for the same job.

Bugfixes to pacify pgsql: changed a non-functional "HAVING" into a nested SELECT, and changed unsupported SUM() into COUNT(CASE … )