updated server processes to use the same latest api functions
removed notification in Persons OnUpdate because it's unclear if this is necessary or not. Has to be fully removed or uncommentedwhen this decision has been made.

Removed the block size configuration from the client. Default value is 5000. All scanners now use the same value, it can be changed via designer custom setting in the preferences
2 fields in the person entity have been added, now the firstname and the lastname fields exist as phonetic and text_no_stopwords
Refactorings

RebuildAllDuplicateCaches_serverProcess.aod takes both person and organisation scanner (currently hard coded) and runs them. This is ought to be executed via the manager/other serverside ways
RebuildDuplicatesCache_serverProcess on the other hand should be used via code because this process expects the filterName and TargetEntity as parameters. The usages are commented out for the time beign becaus of incompatibilities in the process.execute* methods...
If a person or organisation is merged, the standardcommunication ways of the old record are reset to "no standard".

The function ScanForDuplicates has been refactored and is now much more easy to use because it does much more stuff inside to have an easier api.
"RebuildDuplicatesCache" and "ScanForDuplicates" have been refactored.
The fields used in the prefilter don't have to be configured manually by the user. Instead, the fields defined by the prefilter now get added automatically to the list of fields to be used. In the case, that the field has been added via the users config anyways, it doesn't get added by code to ensure that each field is mentioned exactly once.
To reflect these changes, the javadoc including the example of ScanForDuplicates and RebuildDuplicates has been updated.
 Until it's possible to load values from a consumed entity dynamically via code, the possibility to select entity fields from consumed entities via ui has been removed. See ticket #1044577. Now only "native" fields directly from the base entity can be selected.
 Since the entity fields are now used in the configuration of the duplicate search, no db fields have to be configured any more. The field has been removed from liquibase

New Context/Entity/Views/Liquibase to configure which entity fields should be used by the index to search for duplicates
Renaming of DuplicateScanConditionConfig to have a seamless naming system
- DuplicateScanConditionConfig => DuplicateScannerPrefilterConfig
- DuplicateScannerIndexConfig

Es werden sowohl die Organisationscluster angezeigt als auch analog zu den Personen eine Tabelle mit ignorierten Dublettenkombinationen. Entsprechende Aktionen werden ebenso angezeigt.
DuplicatesUnrelated wurde um Logik für Organisationen erweitert
Duplicates wurde um Logik für Organisationen erweitert

Der Serverprozess ist in der ersten Version für das Person_entity fertiggestellt. Es werden die UnrelatedRelations entweder mit der neuen ClusterId geupdatet, sofern die duplicateId Konstellation weiterhin besteht, ansonsten werden die Datensätze gelöscht.