Fix marked played reset position

[flofriday]

Description

Closes: #7144

Remove duplicated marked as played implementation

There were two implementations, one for single items and one for
multiple items. Now we always use the code for multiple items.

I also made API a lot more simpler and the PodDBAdapter now decides if
a the playback position should be reset. Which it will now do if the
we set it to PLAYED but not for NEW or UNPLAYED.

Checklist

• I have read the contribution guidelines: https://github.com/AntennaPod/AntennaPod/blob/develop/CONTRIBUTING.md#submit-a-pull-request
• I have performed a self-review of my code
• I have run the automated code checks using ./gradlew checkstyle spotbugsPlayDebug spotbugsDebug :app:lintPlayDebug
• My code follows the style guidelines of the AntennaPod project: https://github.com/AntennaPod/AntennaPod/wiki/Code-style
• I have mentioned the corresponding issue and the relevant keyword (e.g., "Closes: #xy") in the description (see https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue)
• If it is a core feature, I have added automated tests

Question for the Reviewer

There is currently a bug in this Implementation. If an episode is currently playing the playback position will be reset but since the player is still running it will reset the position within the next second.
If the playback is currently stopped the playback will be reset but reset to the previous position as soon as the user plays the episode again.

What is the best way to solve that? Cause checking for the currenlty playing item it feels wrong to do in PodDBAdapter and also I get a circular dependency warning if I try to include the Playbackservice.

[ByteHamster]

Doesn't the implementation here break the "smart mark as played" feature? I would still keep the overall behavior of the caller deciding whether to reset the position or not.

If an episode is currently playing the playback position will be reset but since the player is still running it will reset the position within the next second. What is the best way to solve that?

I would say like in FeedItemMenuHandler. That class should not do any logic (calling the database etc) and just call the corresponding multi-select method with a Collection.singletonList

[flofriday]

The smart marked as played code was wrong in my opinion. But reading over the code again maybe it is intended if the episode is autoskiped to not reset the playback position. I will revert on that one, however it didn't break smart skip it was only more agressive in resetting the playback position.

[flofriday]

I would say like in FeedItemMenuHandler. That class should not do any logic (calling the database etc) and just call the corresponding multi-select method with a Collection.singletonList

I guess I don't quite get what you mean by that. Do you mean that the caller of the DBWriter methods should find out the playing item and address them differently?