Use ArchiveTraceWorker in ArchiveTracesCronWorker

What does this MR do?

Currently, ArchiveTracesCronWorker (Sidekiq Cron Worker) consumes 1.5~3 GB of memory constantly thus being killed by Sidekiq Memory Killer often. And in this case, the sidekiq job is respawn multiple times in a short interval, for instance, you can see the inconsistent behavior in https://log.gitlab.net/goto/d1432992d790cbaf2744427bd020216f

We should avoid this behavior by splitting archive jobs into individual sidekiq worker. We already have ArchiveTraceWorker for this usage.

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry for user-facing changes, or community contribution. Check the link for other scenarios.
• Documentation created/updated or follow-up review issue created
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Performance 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

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team