UI: Standardize translations and extract tag logic to help check requests

[LuizFNJ]

Description

This PR addresses both issues related to UI consistency and standardization of the Verification Request page. It implements missing translation keys and refactors tag-related logic into reusable helpers.

Related Tickets: #2208, #2209

Changes implemented:

• Internationalization (i18n): Replaced hardcoded strings with translation keys for Severity and SourceChannel tags.
• Code Refactoring: Extracted tag styling (colors) and labeling logic into centralized helper functions to improve maintainability.
• UI/UX Polish: Adjusted layouts, spacings, and alignments within the Verification Request drawer for a more consistent user experience.

Type of change

• Existing feature enhancement (non-breaking change which modifies existing functionality)

Testing

Detailed testing evidence, including screenshots and behavior validation, can be found in the following Notion doc:
Notion PR Evidence - PR #2207

Developer Checklist

General

• Code is appropriately commented, particularly in hard-to-understand areas
• Repository documentation has been updated (Readme.md) with additional steps required for a local environment setup.
• No console.log or related logging is added.
• No code is repeated/duplicated in violation of DRY. The exception to this is for new (MVP/Prototype) functionality where the abstraction layer may not be clear (comments should be added to explain the violation of DRY in these scenarios).
• Documented with TSDoc all library and controller new functions

Frontend Changes

• No new styling is added through CSS files (Unless it's a bugfix/hotfix)
• All types are added correctly

Backend Changes

• All endpoints are appropriately secured with Middleware authentication
• All new endpoints have a interface schema defined

Tests

• All existing unit and end to end tests pass across all services
• Unit and end to end tests have been added to ensure backend APIs behave as expected

Test IDs

• Include the test ID when adding new tasks or components.
• Check that test IDs are present in the modified components.

Merge Request Review Checklist

• An issue is linked to this PR and these changes meet the requirements outlined in the linked issue(s)
• High risk and core workflows have been tested and verified in a local environment.
• Enhancements or opportunities to improve performance, stability, security or code readability have been noted and documented in Project do Github issues if not being addressed.
• Any dependent changes have been merged and published in downstream modules
• Changes to multiple services can be deployed in parallel and independently. If not, changes should be broken out into separate merge requests and deployed in order.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud