[meta] Remove Barriers to GDPR Compliance & Establish Good Defaults in Core

These are the issues that are known to be tied to Drupal Core. This is should be the parent issue of new issues for elements that should be addressed in Drupal Core.

Building in privacy by design requires thinking about how we organize personal information "into account throughout the whole engineering process."

Changing the culture of ICT so that privacy is the default is important.

• #2848974: Privacy Concerns as GDPR Compliance
• #2949017: There is no way to delete file entities of other users
• #2962250: Encrypted storage of fields in core - GDPR support
• #2971791: Drupal Core Search should be configured to search for personal user data
• #2971794: Drupal Core should provide a View with an option to see & export personal information
• #2971798: Ask for privacy consent when a user registers an account
• #2972029: Provide a description of the types of personal data core handles by default
• #2972033: Record of actions on personal data, and purge of these actions.
• #2972035: Provide reminders during installation & administration about compliance requirements
• #2972038: Notify 3rd parties for erasure
• #2972057: Right to restriction of processing
• #2972065: Ensure that watchdog doesn't log personal data with core