Cookies are no longer stored in user metadata when changed.

[AAwouters]

Describe the bug

When logged in, changes in cookie settings were saved in ePerson metadata in dspace 7.6 and 8.
Since the migration from Klaro to Orejime this is no longer the case.

To Reproduce

Steps to reproduce the behavior:

1. Log in
2. Open the cookie settings menu using the link in the footer
3. Change some settings
4. Save the settings
   After saving the settings, a PATCH request should be made to the /api/eperson/epersons/{id} endpoint.
   On the main branch, this is no longer the case.

(Depending on your local branch it is possible no cookie settings can be changed. The branch used by #3613 introduces an optional setting which can be changed.)

Cause

The klaro configuration can accept a callback which is called when the user saves settings.
The orejime configuration does not have a similar property.
The Orejime configuration has a different callback property within the apps array.

This means this line in the browser-orejime.service has no effect, and as a result the orejime settings are not copied to ePerson metadata since the migration to orejime.

Related work

Introduced by #3199.

[tdonohue]

@AndreaBarbasso : Pinging you to make you aware of this bug ticket, as it seems to be related to #3199