[Feature Request] Media Server History by titembaatar

### Description

Media Server Playing & Media Server History custom-api's are amazing as is - thank you! I just have two 'nice to have' requests:

1. Perhaps it's Jellyfin specific, but I'm not able to change the 'history custom-api' code to display all User's history together (like the 'playing custom-api' code does). The workaround was to repeat the code multiple times with different Users in my glance.yml file under a 'Group.' It looks & function good, but even after trying to make ChatGPT as smart as possible about Glance and your code and how it connects with Jellyfin, I couldn't tweak the code to show multiple users in one set of code.
2. The 'playing custom-api' shows Books and Audiobooks, but the 'history custom-api' doesn't. I understand it has something to do with how Jellyfin exposes history for Books/Audiobooks vs. video content, but wondering if there might be a work around or trick to get Jellyfin to cough up the Book/Audiobook history.

- I tried adding, under Options:
media-types: "Movie,Episode,Audio,Audiobook,Book"

- Under template: |
{{ $mediaTypes := .Options.StringOr "media-types" "Movie,Episode,Audio,Audiobook,Book" }}

...and expanded the "cards-horizontal carousel-items-container" list with:
{{ $isAudiobook := eq $mediaType "Audiobook" }}
{{ $isBook := eq $mediaType "Book" }}

- The changes don't cause errors, but also don't work. I know that most people prob don't use Jellyfin, Plex, etc., for books/audiobooks, since there are better apps for that, but it's convenient to consolidate 'all' media under one umbrella and I'm hoping Jellyfin will improve book support someday.

Any thoughts or suggestions would be greatly appreciated! Otherwise, I'll use it as is - which is amazing! Thank you.

Start by comparing the existing history custom-api with the playing custom-api, then review how Jellyfin exposes multi-user history and Book/Audiobook entries. Done would require a clearly defined approach and verified support for the requested history scenarios, but the issue does not identify files or tests.

Written by the indexing model from the issue text.