When Ubuntu packages are updated because of security issues, it looks like their artifacts are published on both -updates and -security repositories. (i.e. libssh)

Currently, to mark a package as a Security update, only the first repo's name is checked (and it is usually the -updates repo), so the package is not marked as a security update.

If there are multiple repositories as origin for a package, this change loops all repos and not just the first one.

• This is partial revert for Update test-cases to work with multiprocess checkAPT. #907 on usr/lib/linuxmint/mintUpdate/Classes.py, line 148

For some security packages, package.candidate.origins looks like this:

[<Origin component:'main' archive:'noble-updates' origin:'Ubuntu' label:'Ubuntu' site:'archive.ubuntu.com' isTrusted:True>,
 <Origin component:'main' archive:'noble-security' origin:'Ubuntu' label:'Ubuntu' site:'security.ubuntu.com' isTrusted:True>]

Fixes #952