manageSnapshots.sh: bug if many arguments are used

Fixes a bug that occures when the script is called with more than 9
arguments
commonLockFcts.sh lock acquisition atomic

functions in commonLockFcts.sh reworked.
A lock is now a folder instead of a file.
This allows to make the lock acquisition atomic (preventing race
conditions in case 2 scripts try to acquire the same lock at the same
time

Functions in commonLockFcts.sh renamed
backupData.sh: compression changed

Compression algorithm changed from gzip to lzjb
2 config parameters renamed

CFG_RUNNING_SCRIPTS_FOLDER renamed in CFG_LOCKS_FOLDER
CFG_FORBID_ANY_SCRIPT_START_FILE renamed in
CFG_FORBID_ANY_LOCK_ACQUISITION_FILE
minor changes in declaration of local var
checkTemps.sh: changes in loging

In parseInputParams: log_warning changes to log_error twice
minor change
minor changes
commonLogFcts.sh: error msg improved in get_log_entries_ts()
commonLockFcts.sh: minor improvements
All scripts: fix undefined lock id & log file name

Some scripts compute the log file name and lock id from the arguments of
the script.
The log file name is required for logging information and errors.
Until now the log functions were sometimes called before the log file
name was known.

The script were corrected so that:
- the log file name and lock-id are not called anymore before the end of
the fct parseInputParams()
- error detected in the fct parseInputParams() are only echoed
- the echoed errors are piped to the log file after the execution of the
fct parseInputParams()
Release notes updated for v1.0-rc4
config.sh: version updated to v1.0-rc4
Merge remote-tracking branch 'origin/master' into exp_backup_remote

Conflicts:
	backupData.sh
	manageAcpi.sh
commonLogFcts.sh: wording corrected