Remove or substitute legacy genome "database ?" metadata when missing in history item displays.

[fubar2]

Describe the bug Ancient wart. Not a bug but now that Galaxy is not just for genomics, it's time to think (again) about why the genome build always appears as history item metadata?

Looking at the news announcement at https://galaxyproject.org/news/2023-06-20-esg-wp5-astronomy-fits/ shows that the new Astronomical image FITS datatype history item displays the genome build metadata as:

database ?

Galaxy has done well for 18 years with this "feature" but the real question is about the utility of metadata in the history display for a dataset. For some data types it could be really useful. Anyone know what would help the user for astronomical image data? UI/UX - need expert help.

Four potential ideas:

1. leave it alone to avoid unintended consequences and remind users to ignore it if they ask what it means.
2. get rid of it altogether. Just remove the genome build metadata from every history item display.
3. make it conditional on the datatype having a non-null genome build as metadata
4. make it configurable and per-datatype specific - create a new history display metadata plugin to allow configuring relevant metadata displays for history items based on the datatype.

That last idea is a lot of work so would need to be sure that having specific metadata display for any given datatype makes the Galaxy history more informative and less confusing for users?

Galaxy Version and/or server at which you observed the bug All

To Reproduce Steps to reproduce the behavior:

1. Go to this news item
2. Look at the metadata displayed in the screenshot.

Expected behavior See above - it's a wart. Not a big wart but confusing and not as helpful as it could be. Situations where metadata can be useful as part of displaying a history item are likely to be specific to particular datatypes. Question for UI/UX experts.

Screenshots

Additional context

[martenson]

xref https://github.com/galaxyproject/galaxy/issues/4484