Revert "Merge branch 'require-source-in-members-update-service' into 'master'"

Purpose of revert

gitlab-org/quality/engineering-productivity/master-broken-incidents#8722 (closed)

Checklist

• Create an issue to reinstate the merge request and assign it to the author of the reverted merge request.
• If the revert is to resolve a broken 'master' incident, please read through the Responsibilities of the Broken master resolution DRI.
• If the revert involves a database migration, please read through Deleting existing migrations.
• Add the appropriate labels before the MR is created. We can skip CI/CD jobs only if the labels are added before the CI/CD pipeline is created.

Milestone info

• I am reverting something in the current milestone. No changelog is needed, and I've added a ~"regression:*" label.
• I am reverting something in a different milestone. A changelog is needed, and I've removed the ~"regression:*" label.

Related issues and merge requests

added Pick into auto-deploy master:broken pipelineexpedited priority1 severity1 labels

added Quality label

mentioned in incident gitlab-org/quality/engineering-productivity/master-broken-incidents#8722 (closed)

assigned to @ddieulivol

Hey @pedropombeiro, Could you please review this revert MR? Thanks in advance

requested review from @pedropombeiro

added backend label

	2 Warnings
	In a revert merge request? Use the revert merge request template to add labels that skip changelog checks. Reverting something in the current milestone? A changelog isn't required. Skip changelog checks by adding ~"regression:*" label, then re-run the danger job (there is a link at the bottom of this comment).
	This merge request does not refer to an existing milestone.

	1 Message
	CHANGELOG missing: If this merge request needs a changelog entry, add the Changelog trailer to the commit message you want to add to the changelog. If this merge request doesn't need a CHANGELOG entry, feel free to ignore this message.

Reviewer roulette

Category	Reviewer	Maintainer
backend	@ahegyi (UTC+2, same timezone as author)	@hustewart (UTC-5, 7 hours behind author)

Please refer to documentation page for guidance on how you can benefit from the Reviewer Roulette, or use the GitLab Review Workload Dashboard to find other available reviewers.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

mentioned in issue gitlab-org/quality/engineering-productivity/internal-rotation#20 (closed)

Proper labels assigned to this merge request. Please ignore me.

@ddieulivol - please see the following guidance and update this merge request.

	1 Error
	Please add typebug typefeature, or typemaintenance label to this merge request.

added typebug label

resolved all threads

approved this merge request

started a merge train

merged

mentioned in commit 95134eba

@ddieulivol This merge request failed to be picked into 17-5-auto-deploy-2024100310 and will need manual intervention.

Create a new merge request targeting 17-5-auto-deploy-2024100310, resolve any conflicts, and assign it to a release manager for merging directly into the auto-deploy branch.

removed Pick into auto-deploy label

mentioned in incident gitlab-org/quality/engineering-productivity/master-broken-incidents#8728 (closed)

mentioned in merge request !167123 (merged)

added workflowstaging-canary label

added workflowcanary label and removed workflowstaging-canary label

mentioned in merge request !168097 (merged)

added workflowstaging label and removed workflowcanary label

added workflowproduction label and removed workflowstaging label

changed milestone to %17.5

resolved all threads

added releasedcandidate label

added releasedpublished label and removed releasedcandidate label