add h265/hevc to deviceCapabilities.tsVideoCodecs

[whiteowl3]

fixes #513
we need to expose a setting or something for this, ultimately, so users can decide whether or not to utilize their server-side tonemapping, if its available to them.

[whiteowl3]

relevant:
jellyfin/jellyfin#7199

[whiteowl3]

actually there is still a subtitle selection issue floating around on titles which my changes cause to directstream instead of transcode on the roku.
I lack the hardware to isolate this tho. if somebody has a roku attached to a dd+ capable device, it would be great to know if you can select subtitles during playback of an HEVC-HDR DD+ 5.1 video file, and if it correctly directplays with these changes.

edit: subtitle issue is happening here: https://github.com/jellyfin/jellyfin/blob/e778877f558bee526b3b4a952e19bebcf560f464/MediaBrowser.MediaEncoding/Subtitles/SubtitleEncoder.cs#L58

edit: this was just an issue with the subtitle profiles.

[whiteowl3]

These lines were removed because they appear in testing to cause containers with two AAC streams to transcode.
Feedback from dmitry lyzo supports this.

 — 
Yesterday at 6:55 PM
As I understand this: device supports AAC in a video or audio file if it is not a secondary track.

Ahh, IsSecondaryAudio: false means client can only use the default or the first track

[whiteowl3]

probably, ALL text subtitles should be added with "external" as long as they comply with https://developer.roku.com/en-ca/docs/developer-program/media-playback/closed-caption.md
(I have no idea which ones do or do not)

[neilsb]

This all seems to work and certainly resolved the hevc issue.