#109638Backend user settings are JSON-encoded twice before being stored in the database
Description
Since #108832, backend user settings are persisted as JSON
in the be_users table, along with an upgrade wizard to
migrate serialized settings to JSON.
Due to a manual json_encode(), values were stored
double-encoded. As a result,
(string)’”{“key”: “some-value”}”’
was persisted instead of the expected
(string)’{“key”: “some-value”}’