Roadmap: Feature by Epics - All Kanban teams IDs in the instance are retrieved when expanding Feature

Issue Summary

In Live Roadmap > Feature By Epics View
When expanding an Epic on the view, if any of the child Feature has a Story assigned to a Kanban Board, the Request URL will include all Kanban Team Ids from the Jira Align Instance, depending on the number of teams it will hit the bug https://jira.atlassian.com/browse/JIRAALIGN-3086

Steps to Reproduce

1. Prepare the hierarchy
   1. Create a Program Without Team Associated
   2. Create a Program Increment and add the Program from Step1
   3. Create an Epic and Assign to Program from Step1.1 and PI from Step1.2
   4. Create a Feature under Epic from Step1.3
   5. Create a Story under Feature from Step1.4
   6. Add the Story from Step1.5 to a Kanban board
2. Go to Live Roadmaps
   1. Set the Configuration bar filter with Program from Step1.1 and Program Increment from Step1.2
   2. Live Roadmap Filters = Work / Feature by Epics / Program Release / Sprint by Program Increment
   3. Click on the Symbol > to Expand the Epic created on Step1.3

Expected Results

The requested URL generated from the roadmap grid to the server should include only the filter parameters that are set on the configuration bar

Actual Results

By having a single story on the work item hierarchy added to any Kanban board, the Request URL generated from the Roadmap grid includes all Kanban Teams ID from the Jira Align instance
Example: The request below, is to expand 1 Epic, with 1 Feature and 1 Story

https://INSTANCE.jiraalign.com/privateapi/kanbanstories?teamId=1376&teamId=1377&teamId=1378&teamId=1379&teamId=1388&teamId=1401&teamId=1417&teamId=1424&teamId=1441&teamId=1454&teamId=1481&teamId=1502&teamId=1504&teamId=1547&teamId=1550&teamId=1564&teamId=1586&teamId=1587&teamId=1595&teamId=1596&teamId=1597&teamId=1598&teamId=1631&teamId=1681

If the customer's instance has a high ammount of Kanban teams it will hit the issue described at https://jira.atlassian.com/browse/JIRAALIGN-3086

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available