Update resource boundary for ExportCsvWorker

What does this MR do?

At the time of writing the last 15 days worth of this job spent more than 50% of its time on CPU. This sets the boundary accordingly.

Visible in this table: https://log.gprd.gitlab.net/goto/e3b176dc7f1ab9efcbfc52e475714e3a

This makes gitlab-com/gl-infra/scalability#177 (closed) possible without having to exclude queues by name

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