deprecate(remove): file write in extractor using to

[tarunKoyalwar]

Proposed Changes

• This PR changes how data is saved when using to in extractors to save extracted data to file

Caution

This is a breaking change and may break templates containing to field in extractors
Saving extracted values to file using to in extractors has been removed due to following reasons

• confliction behaviour since one can achieve this by extracting the same from json output nuclei -j
• data race when template is run with more than 1 target
• out-of-bound write and other considerations

Note

Saving screenshot to file using to has been made with other filesystem restriction options (i.e -lfa) keeping usability in mind. Now when saving screenshots outside of cwd (i.e parent / sibling directories) -lfa will be required

• closes Save to file (extractors) doesn't respect default file system restriction #4564

[Mzack9999]

lgtm - My observations:

• The to: option should probably be replaced with a deterministic output path as we do in httpx to organize request/response/screenshot and report in the output json the path to the file within a field
• Multiple templates might point/access to the same file, probably this particular output mechanisms needs a redesign to simplify them as described above

[Mzack9999]

salute to the 'save to file' feature