Blocking Cookies and Storage Sets (proof of concept)

I just pushed a candidate for testing and discuss.

All cookies and storage items will be blocked until the consent for the service was given.

Two apps are "required" per default:

• Klaro with cookie '^klaro'
• Drupal with cookie '^[SESS|SSESS]'

A new service is published per default:

• CMS Convenience with cookie '^Drupal\.'

All localStorage and sessionStorage e.g. from Drupal (Claro theme or Gin theme) will be blocked until the consent for "CMS Convenience" is given.

All blocked data is written to a local data structure and written to the cookie storage or localStorage / sessionStorage after consent has been given. In this way, no data is lost during blocking.

After revoking consent, not only the cookies will be deleted from Klaro-JS but also the sessionStorage and localStorage.

Please have a look and give feedback.

I also added also an "automatic" mode that open the notice only if neccessary. See screenshot.

@jan kellermann does this require a rebase before it can be tested and reviewed?

Issue branch updated, MR testable without merge conflict.