Filter by iteration in issues list

What does this MR do?

Adds filtering by iteration to:

1. Project issues list
2. Group issues list
3. Project issue board
4. Group issue board

Project	Group

New queries

SELECT
    "issues".*
FROM
    "issues"
    INNER JOIN "sprints" ON "sprints"."id" = "issues"."sprint_id"
WHERE
    "issues"."project_id" = 278964
    AND ("issues"."state_id" IN (1))
    AND "issues"."issue_type" IN (0, 1)
    AND "sprints"."title" = 'gitlab-org: #11'
ORDER BY
    "issues"."created_at" DESC,
    "issues"."id" DESC
LIMIT 20 OFFSET 0

Time: 327.993 ms
  - planning: 0.991 ms
  - execution: 327.002 ms
    - I/O read: 312.913 ms
    - I/O write: 0.000 ms

Shared buffers:
  - hits: 30 (~240.00 KiB) from the buffer pool
  - reads: 144 (~1.10 MiB) from the OS file cache, including disk I/O
  - dirtied: 35 (~280.00 KiB)
  - writes: 0

https://explain.depesz.com/s/UziV

SELECT
    "issues".*
FROM
    "issues"
    LEFT OUTER JOIN "sprints" ON "sprints"."id" = "issues"."sprint_id"
WHERE
    "issues"."project_id" = 278964
    AND ("issues"."state_id" IN (1))
    AND "issues"."issue_type" IN (0, 1)
    AND (sprints.title != 'gitlab-org: #11'
        OR sprints.id IS NULL)
ORDER BY
    "issues"."created_at" DESC,
    "issues"."id" DESC
LIMIT 20 OFFSET 0

Time: 77.441 ms
  - planning: 0.671 ms
  - execution: 76.770 ms
    - I/O read: 75.580 ms
    - I/O write: 0.000 ms

Shared buffers:
  - hits: 1 (~8.00 KiB) from the buffer pool
  - reads: 28 (~224.00 KiB) from the OS file cache, including disk I/O
  - dirtied: 7 (~56.00 KiB)
  - writes: 0

https://explain.depesz.com/s/2nVV

Screenshots

Does this MR meet the acceptance criteria?

Conformity

• [-] Changelog entry
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• [-] Tested in all supported browsers
• [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• [-] Label as security and @ mention @gitlab-com/gl-security/appsec
• [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• [-] Security reports checked/validated by a reviewer from the AppSec team

Related to #118742 (closed)