Add last_played and play_count values to mass.get_queue response

[Laflamme]

We can sort the library by last played and by play count, so I assume some sort of last_played and play_count values are stored in the database. Could those values be included in the mass.get_queue response?

They could be used in automations to skip songs that have played too recently or too often, for example.

[Laflamme]

Those are indeed the values recorded in the database according to server/music_assistant/controllers/music.py:

        if db_item:
            await self.database.execute(
                f"UPDATE {ctrl.db_table} SET play_count = play_count + 1, "
                f"last_played = {timestamp} WHERE item_id = {db_item.item_id}"
            )
        await self.database.commit()

It looks like the file that would need to be modified to include those variables is models/music_assistant_models/player_queue.py.

I'm aware this feature idea has not gotten any traction yet, so I hope this bump is okay. I have very limited coding experience, otherwise I would attempt this myself.