[FEATURE REQUEST] Detect and show FMPS rating

### Is your feature request related to a problem? Please describe. In Namida, I would like to see the 5-star ratings that I created with the Strawberry MP3 player for my MP3 songs. However, Namida claims that most of my MP3s have `0%` rating. This is wrong, as I have set completely different star ratings. Note that Strawberry stores ratings as _FMPS Ratings_ (FMPS = Free Media Player Specifications), with a _Popularity Meter_ fallback. To make this concrete, that means that: * The 5-star ratings (which also support _half_-stars) are mapped to a floating point number (`0.0` to `1.0`, see [here](https://discuss.kde.org/t/amarok-import-mp3s-with-ratings/37942/4) for a table of the in-between values, where the first and last column are the relevant ones). This floating point number is stored in a `TXXX` (User Text Frame) with description = `FMPS_Rating` and something like "0.4" as the string value. * As a fallback, Strawberry _also_ stores the `POPM` (popularity meter) with an empty value for the _email_ and some number between `0 - 255` that is a rough linear interpolation of the 5-star value, mapping it to the 0-255 range. ### Describe the solution you'd like Namida could have a strategy to look for _several_ rating/popularity fields, favoring specific ones first, falling back to generic ones. Concrete example: 1. Look for `FMPS_Rating` TXXX frame and use it. Display a value of 0.2 as 20% 2. If step 1 found nothing, use POPM. Note that the mapping from the 0-255 POPM range to percent (or stars) is _not_ standardized; many MP3 players have a different interpretation! By the way, I honestly have no idea what Namida is currently doing when it comes to ratings. In a quick test, Namida seemed just buggy (tested it with snapshot I downloaded today): I edited the MP3 tags of some MP3 file, typed in a number in the "Rating" field (e.g. `55`) and saved it, then Namida would show "55%", but when I edit the tags again, the value in the "Rating" field has changed to **60** for no apparent reason. ### Describe alternatives you've considered _No response_ ### Additional context _No response_ ### Apps _No response_