Background: If an item has a primary bitstream with an text/html mime type with additional bitstreams in the respective `ORIGINAL` or `CONTENT` bundle, said bitstream is not respected. As in, there's no conditional to filter all the other bitstreams from being listed. This functionality existed in 4.x but was not ported for some reason. Maybe someone could explain to me if this is expected behavior .
Visual example sourced from a client: Example Image
6.x community code base where bitstreams are listed from the METS:
5.x community code base where bitstreams are listed from the METS:
4.x community code base where this case is handled:
Submitting a PR shortly that will be compatible for DSpace 5.x and 6.x