Fixes #5633 - [i18n] Update and complete Hungarian (hu) translations for DSpace 10

[kanasznagyzoltan]

References

• Fixes [i18n] Update and complete Hungarian (hu) translations for DSpace 10 #5633

Description

This PR updates and completes the Hungarian (hu) translations for DSpace 10. It ensures full coverage for new features, including Entities, Relationships, and the improved Workflow, while fixing several syntax issues and outdated terminologies.

Instructions for Reviewers

This PR is a comprehensive update to the Hungarian localization file (hu.json5). We have performed a thorough review of the existing keys and added translations for all missing keys introduced in recent versions.

List of changes in this PR:

• Added missing translations: Full coverage for DSpace 9 and 10 features (Entities, Custom URLs, CMS Metadata hints, LDN services).
• Proofreading & Consistency: Reviewed existing translations to ensure they align with standard Hungarian library and repository terminology.
• Code Cleanup: Removed several hundred lines of outdated "previous version" comments and // TODO markers to improve file maintainability.
• Formatting: Standardized indentation to 2 spaces across the entire file.

Include guidance for how to test or review your PR.

• Build the Angular UI with this branch.
• Switch the language to Hungarian (Magyar) in the UI header.
• Navigate through the following areas to verify translations:
• Submission process: Check new metadata fields and error messages.
• Admin UI: Verify the "Edit User Agreement" and "CMS Metadata" help texts (Markdown notices).
• Search/Discovery: Check facets and entity-related labels.
• Verify that no "missing key" labels (e.g., ???key???) appear in these areas.

Checklist

This checklist provides a reminder of what we are going to look for when reviewing your PR. You do not need to complete this checklist prior creating your PR (draft PRs are always welcome).
However, reviewers may request that you complete any actions in this list if you have not done so. If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!

• My PR is created against the main branch of code (unless it is a backport or is fixing an issue specific to an older branch).
• My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
• My PR passes ESLint validation using npm run lint
• My PR doesn't introduce circular dependencies (verified via npm run check-circ-deps)
• My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
• My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
• My PR aligns with Accessibility guidelines if it makes changes to the user interface.
• My PR uses i18n (internationalization) keys instead of hardcoded English text, to allow for translations.
• My PR includes details on how to test it. I've provided clear instructions to reviewers on how to successfully test this fix or feature.
• If my PR includes new libraries/dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
• If my PR includes new features or configurations, I've provided basic technical documentation in the PR itself.
• If my PR fixes an issue ticket, I've linked them together.