Combine FileArtifactExtractionTask and Analysis Tasks

We should combine some of the Tasks that have one to one mappings of FileArtifactExtractionTasks to a given Analysis Task as there is not much benefit to separating these into separate tasks unless there are multiple tasks that can use the same artifact type. We have a couple options:

1. Change analysis tasks to use the file artifact utility and have the jobs create those directly
2. Consolidate all artifact extractions into a single artifact extraction task that generates extracted artifacts for each of the different types we need.

No files, tests, or entry points are named. Start by locating the FileArtifactExtractionTask, the analysis tasks with one-to-one mappings, and the file artifact utility. Compare the two proposed designs and define a complete task and artifact flow before implementation; done means the selected consolidation works without breaking artifact consumers.

Written by the indexing model from the issue text.