SLT-1164: Make sure gdprDump generates unique usernames in user_field_data

[k4lv15]

Motivation

• Current gdprDump config for user_field_data.name field doesn't check the uniques of the generated value, thus it can lead to entries with duplicate "names". That is against Drupal user_field_data DB table/index rules (see below) and would lead to errors in reference DB import, thus missing data.

This issue can present itself on large sites with thousands of users (i.e., 35k) as there is a hight change of gdprDump generating entries with duplicate usernames as I believe those are not completely randomized but rather generated from a given set of "names", "surnames", "titles" etc.

Changes proposed:

• Make sure unique usernames are generated by gdprDump by explicitly setting unique: true property

Pull Request Overview

This PR aims to address the issue with duplicate usernames generated by gdprDump that can cause database conflicts in Drupal's user_field_data table.

• Adds a new configuration to enforce unique username generation.
• Updates the values.yaml file by adding the "unique: true" option under the user_field_data.name field.

Comments suppressed due to low confidence (1)

charts/drupal/values.yaml:510

• Consider adding tests to verify that the gdprDump now consistently generates unique usernames when the 'unique' flag is enabled, ensuring compliance with Drupal's DB schema.

unique: true