Version:

• listmonk: v5.0.0
• OS: official Docker image

Description of the bug:
When there are scheduled campaigns for day 1, day 7, day 14, etc., for a list with only a few subscribers, and all subscribers unsubscribe before the next scheduled campaign, the campaign state does not update correctly and listmonk tries to send the campaign in a loop.

In fact, when planning a campaign on an empty list, the campaign remains in the "Planned" state at the scheduled time. In version 3.x, the state would change to "Finished."

Steps to Reproduce:

1. Plan a campaign on an empty list (non-planned campaigns work as expected)
2. On scheduled time, the campaign remains in Planned state (in v3.x it changed to Finished)

Additional Notes:
When there are files attached to the campaign and those files are stored on a S3 bucket, a large number of requests are made to the bucket. This results in excessive costs due to the very high volume of requests.