Part 2 - Artifact download migration to graphql

What does this MR do?

Issue	Description
#328194 (closed)	Creates 2 new artifact download components
#328481 (closed)	Uses 2 new components, and deletes old components <-- THIS MR

Summary of things done:

• Swap out fuzzing-artifact-download component for the newer components
• Delete old fuzzing-artifact-download component, its specs, and usages.

Video Demo

https://youtu.be/M0GlSy62lD8

Screenshots (strongly suggested)

Merge Request Page:

Pipelines Page -> Security Tab:

Does this MR meet the acceptance criteria?

Conformity

• 📋 Does this MR need a changelog?
  • I have included a changelog entry.
  • I have not included a changelog entry because _____.
• 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

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

Related to #328481 (closed)