Metadata description for `id` is confusing

[theosanderson]

The metadata description is something like this:

This is pretty confusing, and we only need fastaId in the multisegmented case - we should make this description configurable per organism and generally improve it.

[theosanderson]

@theosanderson-agent try to make something where if description is set for id on a per-organism basis in values.yaml this information (and any other fields) are pulled out and used instead of the one hardcoded in the template. Make a PR.

[theosanderson-agent]

I've created a draft PR at #6077 that adds per-organism idFieldOverrides to the schema config.

Operators can now set displayName, definition, guidance, and example for the id input field under each organism's schema.idFieldOverrides in values.yaml. When not set, the existing hardcoded defaults are preserved.

Example usage:

organisms:
  my-organism:
    schema:
      idFieldOverrides:
        definition: "Sample identifier"
        guidance: "Enter the unique sample ID from your lab system."

[theosanderson]

Ah, also atm these field descriptions are hardcoded in website code, which isn't good generally - we can address that too

[anna-parker]

Ah I noticed this on @maverbiest's PR as well: #6066 - and made some suggestions, but yeah good to do this in a separate PR