Ignore sorting parameter when exporting issues to CSV

What does this MR do?

When exporting issues to CSV, we pass same parameters (sorting, filtering) as used on issues index page. There is no reason to call IssuesFinder with sorting parameter because then IssuesFinder may generate much more complex query for getting issues (depending on what column is used for sorting) and this sorting is then ignored anyway by CSV Builder because it uses .find_each to load issues in batches.

Are there points in the code the reviewer needs to double check?

Why was this MR needed?

Screenshots (if relevant)

Does this MR meet the acceptance criteria?

• Changelog entry added, if necessary
• Documentation created/updated
• API support added
• Tests added for this feature/bug
• Conforms to the code review guidelines
  • Has been reviewed by a UX Designer
  • Has been reviewed by a Frontend maintainer
  • Has been reviewed by a Backend maintainer
  • Has been reviewed by a Database specialist
• EE specific content should be in the top level /ee folder
• Conforms to the merge request performance guidelines
• Conforms to the style guides
• Conforms to the database guides
• If you have multiple commits, please combine them into a few logically organized commits by squashing them
• Internationalization required/considered
• If paid feature, have we considered GitLab.com plan and how it works for groups and is there a design for promoting it to users who aren't on the correct plan
• End-to-end tests pass (package-and-qa manual pipeline job)

What are the relevant issue numbers?

Closes #4159 (closed)