fix: fixing run number in dataset list (#1976)

## Description
This PR removes the custom function to extract the run number from the
scientific metadata with hard coded key name. It instead uses the
dedicated high level field run_number recently added in the dataset
schema.

<img width="1530" height="923" alt="SciCat_dataset_run_number_fix_1"
src="https://github.com/user-attachments/assets/b03b1d3c-4a07-40ed-8032-0e91145333ec"
/>

<img width="1530" height="923" alt="SciCat_dataset_run_number_fix_2"
src="https://github.com/user-attachments/assets/172907c4-e4de-40af-bbf2-517b19c129fd"
/>


## Motivation
We need to show run number high level field by default. A soon to be
created PR, will allow to include scientific metadata in the datasets
list, so a different run number from scientific metadata will be
addressed by the new PR.

## Changes:
Please provide a list of the changes implemented by this PR
* datasets table

## Tests included
- [ ] Included for each change/fix?
- [ ] Passing? (Merge will not be approved unless this is checked) 

## Documentation
- [ ] swagger documentation updated \[required\]
- [ ] official documentation updated \[nice-to-have\]

### official documentation info
If you have updated the official documentation, please provide PR # and
URL of the pages where the updates are included

## Backend version
- [ ] Does it require a specific version of the backend
- which version of the backend is required:

## Summary by Sourcery

Fix run number display in the dataset list by removing the custom
scientific metadata fallback and using the high-level runNumber field,
add localization of table headers, and standardize translation
namespaces across dataset components.

Bug Fixes:
- Use the high-level runNumber field for the dataset list instead of the
scientificMetadata fallback

Enhancements:
- Inject TranslateService to translate dataset table column headers
using the "dataset" namespace
- Unify translation context to "dataset" in both dataset-detail
components

Chores:
- Add console.log statements in DynamicMatTableComponent for debugging

Author: nitrosx

src/app/datasets/dataset-table/dataset-table.component.ts

@@ -271,10 +271,7 @@ export class DatasetTableComponent implements OnInit, OnDestroy {
     if (event === TableEventType.SortChanged) {
       const { active, direction } = sender as Sort;
 
-      let column = active;
-      if (column === "runNumber") {
-        column = "scientificMetadata.runNumber.value";
-      }
+      const column = active;
 
       this.store.dispatch(sortByColumnAction({ column, direction }));
     }
@@ -367,8 +364,7 @@ export class DatasetTableComponent implements OnInit, OnDestroy {
 
   onSortChange(event: SortChangeEvent): void {
     const { active, direction } = event;
-    let column = active.split("_")[1];
-    if (column === "runNumber") column = "scientificMetadata.runNumber.value";
+    const column = active.split("_")[1];
     this.store.dispatch(sortByColumnAction({ column, direction }));
   }
 
@@ -387,13 +383,6 @@ export class DatasetTableComponent implements OnInit, OnDestroy {
           tooltip: column.tooltip,
         };
 
-        if (column.name === "runNumber" && column.type !== "custom") {
-          // NOTE: This is for the saved columns in the database or the old config.
-          convertedColumn.customRender = (c, row) =>
-            lodashGet(row, "scientificMetadata.runNumber.value");
-          convertedColumn.toExport = (row) =>
-            lodashGet(row, "scientificMetadata.runNumber.value");
-        }
         // NOTE: This is how we render the custom columns if new config is used.
         if (column.type === "custom") {
           convertedColumn.customRender = (c, row) =>

src/app/shared/modules/dynamic-material-table/table/dynamic-mat-table.component.ts

@@ -553,7 +553,6 @@ export class DynamicMatTableComponent<T extends TableRow>
     if (column.customRender) {
       return column.customRender(column, row);
     }
-
     return row[column.name];
   }