since all the signature badge templates now have more or less the same
content we can push most of it down to the main template `_signature_badge`.

This is faster for the deployment process, as the destroyed signatures
will be re-generated on demand again, instead of updating them all on
deploy.

To avoid having to implement legacy code handling for the obsolete
`verified_signature` attribute and to avoid any race conditions during
the zero-downtime-deployment we do the following:

1. Destroy all records
2. Migration: Use add_column_with_default to add the new attribute and
   update the verification_status values on records created between 1.
   and 2.
3. Deploy the new code
4. Post migration: Destroy all records

Like this we make sure that at no point there is a record with a `nil`
value for the new `verification_status` attribute.

this is used to make a difference between a committer email that belongs
to user, where the user used a different email for the gpg key. this
means that the user is the same, but a different, unverified email is
used for the signature.

this is necessary for email comparisons

the updated verification of a gpg signature requires the committer's
email to also match the user's and the key's emails.

we need the commit object for the updated verification that also checks
the committer's email to match the gpg key and user's emails.

Add my_reaction_emoji param to /issues and /merge_requests API

See merge request !14016

Extend API: Pipeline Schedule Variable

Closes #34518

See merge request !13653

Merge branch 'fix/sm/35650-remove-createtriggerrequestservice-and-forbid-to-persist-variables-on-ci-triggerrequest' into 'master'

Removes `CreateTriggerRequestService` and add a blocker to prevent saving variables on `Ci::TriggerRequest`

Closes #35650

See merge request !13792

Implement `failure_reason` on `ci_builds`

Closes #37239

See merge request !13937

Fix CI/CD `types` config entry removal due date

See merge request !13990

Added support for additional time series charts

Closes #33345

See merge request !13159

Make project selection dropdown for issue editing consistent

See merge request !13574

Make transfer project dropdown in project settings consistent

See merge request !13596

Make target branch dropdown on merge request edit page consistent

See merge request !13592

Make protected branches / tags permission dropdowns consistent

See merge request !13611

Make dropdowns on new issue page consistent

See merge request !13584