Closed iterations still show in issues detail

Summary

Iterations that are already closed with past dates still show when selecting an iteration for some issue.

Steps to reproduce

1. Create an iteration
2. Wait until it closes (after due date)
3. Create a new issue
4. Save issue
5. Access details of issue
6. Search for iterations
7. Notice the closed iteration still shows, different than a milestone, that only opened and upcoming shows.

This is a problem, since there will be "tons" of closed iterations, and it will be very hard to search for the opened/upcoming ones.

What is the current bug behavior?

Closed iterations show in list for assignment in an issue.

What is the expected correct behavior?

Only opened and upcoming iterations should appear on the list.

Proposal

We already support adding a state parameter to the iterations GraphQL object, so all that has to happen is for us to change the query being used to populate the dropdown to send state: "opened", which would return all upcoming and started iterations.

Relevant logs and/or screenshots