Backend changes for the tickets under OP-3668. Added the migrations shown in the ticket with added dct source. For the second ticket de mu-search indexing config was changed. (Notice for testing, you need to run scripts/reset-elastic.sh to test).
The indexes for the municipality and province of a position's organisation are
not used in the app. Removing them to decrease the time required to index data.
This makes diff'ing the dev and prod configurations for the `search` service
slightly more readable.
- use same order of eager index entries with prod confiuration
- remove an extra normalizer setting in the dev config
- remove duplicate person id index
- correct property name in identifier mappings
- add missing `first_name_used` mappings
- order properties and mappings consistently across file
Index municipality names as keywords instead of as plain text. This prevents
them from being split at word separators. Thereby avoiding that searches for a
municipality name, as used by the frontend's municipality filter, return
organisations whose municipality is a partial match.
For example, previously the results when searching for "Puurs" also included the
organisations located in "Sint-Amands-Puurs". The latter was tokenized into
three terms, therefore also matching plain "Puurs". By treating the municipality
name as keyword this split non longer happens.
Soon we want to introduce (additional) non-administrative unit
organizations. This renaming makes it more clear this index is not limited to
administrative units, both here as where it is used in the frontend. Note,
technically the 'units' name was already incorrect as a 'Representatief orgaan'
is not an administrative unit.
