Issue View should load children section with pagination to improve performance

In a scenario in which a parent issue has way too many children to be displayed, the page load of the parent issue view is drastically impacted.

We had a case that an Epic had 1122 child issues and that would make the Epic issue view load to take up to ~45 seconds to load.

This could be addressed by creating some sort of pagination that would only display the first set of child issues at first and have an option to the see the next page and so on just like filter results are made.