Scheduling wrongly plan work for the first release even if released or in the past

For Kanban team, the first available piece of work is assigned to the first list release even if it's far in the past. The next piece of work is then assigned to the next release matching today's date as expected.

Releases in Portfolio only `disappear` when archived, so this even happens on versions marked as `Released`.

To reproduce:

• Create a kanban team
• Create an issue with an estimate and no release assignment
• Add a release started/released way back in the past (optionally mark it as released in JIRA)
• Calculate

The issue will be assigned to the past release wrongly. Switching the team to scrum shows the correct behavior.