fix(visual-editor): bridge DB field type to hardcoded translation key

The previous commit used translateService.instant(dbType.type) directly,
but DB type strings like "ShowPdf" don't match the translation keys
like "ShowPDF". Now bridge via the enum member name: look up the DB
type by id, then find the hardcoded entry whose enum name matches
(case-insensitive), and use its name as the translation key. Falls
back to the raw DB type string for unknown types.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: renemadsen

eform-client/src/app/modules/eforms/eform-visual-editor/components/eform-visual-editor-elements/field/visual-editor-field/visual-editor-field.component.ts

@@ -9,6 +9,7 @@ import {
 } from 'src/app/common/models';
 import {
   eformVisualEditorElementColors,
+  eformVisualEditorElementTypes,
 } from '../../../../const';
 import { LocaleService, EFormService } from 'src/app/common/services';
 import {TranslateService} from '@ngx-translate/core';
@@ -83,10 +84,15 @@ export class VisualEditorFieldComponent implements OnInit, OnDestroy {
       return '';
     }
     const dbType = this.dbFieldTypes.find(x => x.id === fieldType);
-    if (dbType) {
-      return this.translateService.instant(dbType.type);
+    if (!dbType) {
+      return '';
     }
-    return '';
+    const hardcoded = eformVisualEditorElementTypes.find(e =>
+      EformFieldTypesEnum[e.id]?.toLowerCase() === dbType.type.toLowerCase()
+    );
+    return hardcoded
+      ? this.translateService.instant(hardcoded.name)
+      : dbType.type;
   }
 
   ngOnInit() {