user_ldap 0.19.1 release

This is the server app release template, please copy the part below in a new ticket. For instructions around app releases, see https://kiteworks.atlassian.net/wiki/spaces/OG/pages/404326697/Releasing+Apps

[x] Verify transifex commits (enterprise should update weekly, others daily): If folder l10n exists, then git log should show '[tx] updated from transifex` ...
[x] Check info.xml description and screenshot

[x] Create QA Milestone and set the description to $version
[x] Create release branch with the format "release-$version"
[ ] Create "$version Testplan" (QA templates or Enterprise)
[ ] copy new/reopened issues from the previous release ticket as 'Issues to review' below.
[x] check if Non-normal Release Process applies, and adapt this checklist.

[x] Changes in the docs needed? If so create issue in https://github.com/owncloud/docs-server/issues/new .

All actions to be done on the release branch (git pull; git checkout -b release-x.x.x) from here:

[x] Bump version in appinfo/info.xml (no version suffix)
[x] Check php version dependency and minimum ownCloud version dependency in appinfo/info.xml
[x] Bump "sonar.projectVersion=" in sonar-project.properties (no version suffix)
[x] Change CHANGELOG.md 'Unreleased' to '$version' (today's date)

[ ] git tag -s v${version}-rc.1 on release branch
[x] Build and sign RC tarball from github tag v${version}-rc.1 (see handbook for how to build)
[x] Check buildlog for security reports
[x] Check github security tab dependabot reports
- [ ] -> if critical or high entries are reported: open a release blocker issue.
[x] Upload as Github release using changelog entries
[x] Test and document in testplan + manual explorative testing:
- [ ] If this is an enterprise app: Enabling the app must start the grace period
- [ ] Add section "Changlog Testing" using github releases text or CHANGELOG.md from release branch
- [x] Do changelog tests
- [ ] Do regression tests
- [ ] Watch out for untranslated strings when locale is de oder de_DE.
- [x] => Final "Go" from QA (set 'QA-ready' label) => else do another RC after fixing issues in the "release-$version" branch

[x] Upload tarball to marketplace (details https://kiteworks.atlassian.net/wiki/spaces/OG/pages/404326697/Releasing+Apps)
[x] Publish tarball for customers github/owncloud/QA/tools/portal_upload_app.sh - old 10, old 10.0 and new portal (details https://kiteworks.atlassian.net/wiki/spaces/OG/pages/404326697/Releasing+Apps)
[ ] Send mail to release-coordination with link to this ticket and to the changelog github/owncloud/QA/tools/release/oc_release.sh app:status
[ ] Submit mail-text as a Markting Request via https://kiteworks.monday.com/boards/5983659465/views/130504071 using login name + password, (not SSO)
- Prompt: convert into 5 lines of enduser friendly marketing language, nothing exciting, no exclamation marks, this release is a minor update only:
- paste email text, review and edit result.

[x] Add a new 'Unreleased' section in CHANGELOG.md (and also update links at the bottom!)
[x] Create PR to merge changes back to the master branch with description "Closes #XYZ" with the release ticket number
[x] Rename QA milestone to $version and close the milestone
[ ] Update https://kiteworks.atlassian.net/wiki/spaces/PROD/pages/403801090/Upcoming+Releases
[x] Ensure release template is up to date
[x] Ensure the testplan template (community or enterprise) is up to date
[x] Close the testplan issue
[x] Check for any left over TODO's at https://kiteworks.monday.com/my_work (hide [x] done, empty)

owncloud / user_ldap