[Spike] Determine which Job Artifacts we will scan for secrets

Summary - Why is this spike needed?

We are working on technical discovery efforts to determine how we can expand Secret Detection to Job Artifacts. As a part of this effort, we need to determine what qualifies as a Job Artifact, what their formats are, and decide which ones we'll support in each shippable iteration of this feature (Experiment, Beta, GA).

Requirements

• Define what a job artifact is and what we should expect at the completion of a job
• Put together a list of all arbitrary files that can be included in a job artifact, including types of formats for each.
• Determine the effort/complexity required to expand scanning to each artifact format
• Work with EM/PM to prioritize which artifact types will be included in each shippable iteration

Timebox Expectations

TBD

Expected Outcomes

• Job Artifacts definition and list are added to the parent issue/epic.
• Each shippable iteration has a clear list of job artifacts we'll be expanding to
• Determine how artifacts are bound (by file type, size, etc.) and the performance implications associated with them

Additional context