Fix swimlane problem

What does this MR do and why?

Fixes a bug where issues were appearing under both their direct parent epic and ancestor epics in Epic swimlane board views. This caused board clutter and defeated the purpose of the epic hierarchy.

The root cause was that includeSubepics was implicitly true in the GraphQL requests made by the Epic swimlanes components. This MR sets includeSubepics: false explicitly in:

• EpicLane — when fetching issues for a specific epic lane
• EpicsSwimlanes — when fetching epics (both initial load and pagination via fetchMore)

When Epic swimlanes are enabled, issues should always appear only under their direct parent epic, regardless of any active filters. The includeSubepics: true behavior (showing full hierarchy) is only appropriate in non-swimlane contexts where a user explicitly filters by a parent epic.

References

Closes #598681 (closed)

Screenshots or screen recordings

Before	After

How to set up and validate locally

Please see the clips to see how to validate locally or instructions in the issue.

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.