Avoid analyzing generated configuration file

[henrymercer]

Store the generated config file in temporary directory to prevent it from becoming part of the analysis.

Merge / deployment checklist

• Confirm this change is backwards compatible with existing workflows.
• Confirm the readme has been updated if necessary.
• Confirm the changelog has been updated if necessary.

[angelapwen]

Looks fine, though do we expect the config file to affect the analysis in some way if it's not in the temp directory?

[henrymercer]

Since it's a YAML file it'll be included in JavaScript extraction by default. I noticed when I was trying to create a "no code found" error, but despite no JS or YAML being in the repository, the JavaScript analysis successfully extracted the configuration file and therefore didn't error.