Spotted in the publisher logfile.

SCM/CI: Improve storing projects and packages for setting flags

[src/api] Update nokogiri 1.16.3 → 1.16.4 (patch)

Before, we stored (performed one call to the backend) a project or a
package for every flag set with the SCM/CI integration set_flag step.

From now on, we store only once for every single project or package.

do not compare patches for different CVE or bug entries, these
can not be compared like patches for different versions would

Use the proper icon for relationship notifications

[src/api] Update rubocop 1.63.0 → 1.63.1 (patch)

Escape project and package title

The relationship notifications shouldn't take the notifiable_type into
account, all of them (for project or package) will have the same icon.

When updating the title within an AJAX call, it crashed when the
title contained quotes. Escaping the title was missing.

When updating the title within an AJAX call, it crashed when the
title contained quotes. Escaping the title was missing.

[src/api] Update mocha 2.1.0 → 2.2.0 (minor)

Eliminate caching of revisions and fetch them directly from the backend

Adjust error message for failed submit

Allow mentioning users with plus sign in the name

Update cop namespace

When the project is not found.

Usernames like `cat+factory` are now handled correctly in comments
mentions.

[src/api] Update ajax-datatables-rails 1.4.0 → 1.5.0 (minor)

Better placeholder text

Refactoring TriggerWorkflowController

[backend] do not send resumeproject events to the signer

When doing a copybuild we clobber the arch to 'signer' if something
needs to be signed. When we do delayed linking and we want to
send the resume, we must use the original architecture.

[backend] support product compose name schema on release

Support ftp tree and iso names of composer

[backend] support a "startbefore" parameter in source _history queries

Avoid double encoding parameters to the backend

Update rails to version 7.0.8.1