This patch:
- fixes the problem with "add --redo"
- fixes the problem with overloaded server because of check_and_split_data
- adds a directive in openit.cfg, "COMPRESSION", which will default to "global=none,temp=none". By
setting the temp to "gzip", and restarting the server, temporary files in the server will be
compressed with gz format.
- modifies Archiver to handle .gz incoming files besides of plain .in files
- makes a directory for incoming/archiver and moves archiver files into it to speed up processing of
check_and_split_data to avoid overloading of server.
- fixes issue with check_and_split_data failing to process files with timed out lock
- fixes issue with check_and_split_data hanging if lock files are accumulated in the incoming
directory

The following perl modules, scripts, and binaries are updated:
* Config.pm
* DataLoader.pm
* DataTypes.pm
* Defaults.pm
* File.pm
* FileHelper.pm
* FileLock.pm
* FileObject.pm
* Server.pm
* Protocol.pm
* add
* check_and_split_data
* merge_raw_data
* filtrator
* archiver
* calcchecksum
* summasummarum

merge_psm_data is added to support compression of temporary data in the server.

This patch updates Filtrator to fix the warning messages that are not recognized.

This patch contains a new feature called ‘Advance Mapping’ which can be configured to
include-exclude data like products and features. This feature can be utilized when merging data and
excluding the unwanted data.

Usage:
The configuration is the same as a normal mapping but prefixes should be added to indicate if it’s
to be included or excluded. Adding ‘+’ or no prefixes on a name means it is included, adding ‘-’ on
a name means it is excluded. Entries are evaluated from bottom-up.

The mapping type should also be set as 'ADVMAP'.

Example:

 	ADVMAP: Combined_Product
   	+*;licsrv
   	-server01_legacy;licsrv

This means all products that match(es) ‘*;licsrv’ will be included and 'server01_legacy;licsrv' will
be excluded in the mapping.

NOTE:

- Prefixes mentioned cannot be used for regular MAP setup.
- Advance Mapping is not recommended for rename functions.
- While ADVMAP enables a more advanced method for mapping, it is also slower. It can be significant
for huge data sets.