Conflicts:
	.liquibase/Data_alias/basic/_demoData/generatedData/AB_ATTRIBUTERELATION.xml
	.liquibase/Data_alias/basic/_demoData/generatedData/AB_OBJECTRELATIONTYPE.xml
	.liquibase/Data_alias/basic/_demoData/generatedData/ACTIVITY.xml
	.liquibase/Data_alias/basic/_demoData/generatedData/ADDRESS.xml
	.liquibase/Data_alias/basic/_demoData/generatedData/CAMPAIGN.xml
	.liquibase/Data_alias/basic/_demoData/generatedData/CAMPAIGNCOST.xml
	.liquibase/Data_alias/basic/_demoData/generatedData/CAMPAIGNSTEP.xml
	.liquibase/Data_alias/basic/_demoData/generatedData/CLASSIFICATIONTYPE.xml
	.liquibase/Data_alias/basic/_demoData/generatedData/COMMUNICATION.xml
	.liquibase/Data_alias/basic/_demoData/generatedData/CONTACT.xml
	.liquibase/Data_alias/basic/_demoData/generatedData/CONTRACT.xml
	.liquibase/Data_alias/basic/_demoData/generatedData/DESCRIPTIONTRANSLATION.xml
	.liquibase/Data_alias/basic/_demoData/generatedData/DOCUMENTTEMPLATE.xml
	.liquibase/Data_alias/basic/_demoData/generatedData/FORECAST.xml
	.liquibase/Data_alias/basic/_demoData/generatedData/OBJECTMEMBER.xml
	.liquibase/Data_alias/basic/_demoData/generatedData/OFFER.xml
	.liquibase/Data_alias/basic/_demoData/generatedData/OFFERITEM.xml
	.liquibase/Data_alias/basic/_demoData/generatedData/ORGANISATION.xml
	.liquibase/Data_alias/basic/_demoData/generatedData/PERSON.xml
	.liquibase/Data_alias/basic/_demoData/generatedData/PRODUCT.xml
	.liquibase/Data_alias/basic/_demoData/generatedData/PRODUCTPRICE.xml
	.liquibase/Data_alias/basic/_demoData/generatedData/SALESORDER.xml
	.liquibase/Data_alias/basic/_demoData/generatedData/SALESORDERITEM.xml
	.liquibase/Data_alias/basic/_demoData/generatedData/SALESPROJECT.xml
	.liquibase/Data_alias/basic/_demoData/generatedData/SALESPROJECT_MILESTONE.xml
	.liquibase/Data_alias/basic/_demoData/generatedData/SALESPROJECT_TOUCHPOINT.xml
	.liquibase/Data_alias/basic/_demoData/generatedData/SALUTATION.xml
	.liquibase/Data_alias/basic/_demoData/generatedData/TASK.xml
	.liquibase/Data_alias/basic/_demoData/generatedData/TICKET.xml

Changed liquibase files accordingly.

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

replace all keywords in liquibase which are filled with spaces to 36 chars by the same keyword without the spaces

New field BLOCK_SIZE which specifies the bulk size of data which gets loaded. This is used in the case of a cache rebuild, the data to scan for duplicates gets loaded in the thru BLOCK_SIZE specified size.

Feld DB_FIELD_NAME removed
Created fields for defaultvalues city,zip,... to use in duplicatesearchconfig
Custom fields added in subProcess to have them added to the index

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

[Projekt: Entwicklung - Neon][TicketNr.: 1034308][Liquibase funktioniert  nicht mit MariaDB/Mysql an manchen Stellen]

The editview has been integrated in the general duplicatescanner editview.

The Indexfieldconfig now contains the correct fields which are necessary to run the search.
The fields now can be configured via the client. Those infos are now used to dynamically load the configured fields an their values which are then internally used to run the prefilter as well as the real duplicate search.
NEXT UP => Configuring of the result fields. There's light at the end of the tunnel.