Read-only filesystem fixes for when ~/.config is not writable

[S4lt5]

Proposed changes

When running nuclei in a lambda function, I ran into the issues described in #3576.

I've been using the changes locally for a few months with great success, but I understand that this might break existing installs so I am not sure if this is something that will even be considered.

I know there is a bit of testing and etc to sort out, but as I have not done any nuclei PRs out side of the templates project, I figured the best course of action was just to start a PR and get a dialog going.

Checklist

• Pull request is created against the dev branch
• All checks passed (lint, unit/integration/regression tests etc.) with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

[tarunKoyalwar]

@Yablargo thanks for PR , we are in middle of adding this support across all projectdiscovery tools see: projectdiscovery/goflags#114 . its currently in functional testing phase ( it will migrate all existing configs from old directory to new one ) . we will roll out this in nuclei and other tools soon after more testing .

Thanks , meanwhile you can try projectdiscovery/goflags#114 and share if you face any issues

[tarunKoyalwar]

closing this as the issue was resolved in #4228