Backend Consent Propagation and Existing User Consent Flow Updates

[pattisdr]

❗ Blocked by #2832

Is your feature request related to a specific problem?

• Updates the existing consent propagation code (part of the privacy request execution framework) to factor in that data uses should be considered when determining whether to make an API call or send an email to a third party service in a backwards compatible way. We currently just fire all requests that are defined provided certain prerequisites are met.
• Factor in new field: enforcement_level (frontend or system_wide) as to whether or not we should propagate preferences to third party systems.
• Updates the existing endpoint that saves user consent preferences after they have verified their identity. This should be done in a backwards compatible way to work both with the privacy center API that reads from the config.json file and the new UI that will read from privacy notices.

Describe the solution you'd like

See Design Doc Consent Propagation and Existing User Consent Flow

Describe alternatives you've considered, if any

A description of any alternative solutions or features you've considered.

Additional context

Add any other context or screenshots about the feature request here.

[pattisdr]

I am closing this ticket as the entire approach has changed and reticketing