Fix - Use dropdown translation in generated ticket content

[erique-souza]

Checklist before requesting a review

• I have read the CONTRIBUTING document.
• I have performed a self-review of my code.
• I have added tests that prove my fix is effective or that my feature works.

Description

• It fixes Service catalog breadcrumb and generated ticket content ignore DropdownTranslation #25249

QuestionTypeItem::formatRawAnswer() reads the raw completename / friendly name
of the answered item, so the value frozen into the generated ticket content and
title is always in the source language, even when a DropdownTranslation exists
for the requester's language.

The ticket content is built once at submission time and stored in
glpi_tickets.content, so the value has to be resolved at that moment — there is
no later render that could apply the translation.

The other fields['completename'] read in this file, in
transformConditionValueForComparisons(), is deliberately left alone: conditions
must compare against the source value, otherwise form logic would depend on the
viewer's language.

The breadcrumb half of the issue is already fixed on 11.0/bugfixes by #24678,
so it is not included here.

Added testFormatRawAnswerUsesDropdownTranslation as a non-regression test: it
builds a Location tree, adds an fr_FR translation, logs in as a French user
and asserts the translated value is returned.

Reproduced and verified on a production instance running 11.0.8, pt_PT install
with en_GB users, applied via a bind-mount over the container file.

[trasher]

Tests are failing, please check

[Rom1-B]

Please fix CI

[trasher]

Tests fails