Purge cache on global callback set

[Mzack9999]

Proposed changes

This PR invalidates internal cache in case of global callback settings which are hold as reference inside template executor. The proper solution would be to have a global parsing logic and executor compilation that should happen in ephemeral lazy mode.

Closes #4836

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)

Example

go snippet

package main

import (
  "fmt"

  nuclei "github.com/projectdiscovery/nuclei/v3/lib"
  "github.com/projectdiscovery/nuclei/v3/pkg/output"
)

func run() {
  ret := make([]*output.ResultEvent, 0, 10)
  ne, err := nuclei.NewThreadSafeNucleiEngine()
  if err != nil {
  	return
  }
  cb := func(event *output.ResultEvent) {
  	ret = append(ret, event)
  	fmt.Printf("%p, %v\n", ret, ret)
  }
  ne.GlobalResultCallback(cb)

  tf := nuclei.TemplateFilters{IDs: []string{"exposed-redis"}}
  opts := []nuclei.NucleiSDKOptions{
  	nuclei.WithTemplateFilters(tf),
  }
  err = ne.ExecuteNucleiWithOpts([]string{"127.0.0.1:6379"}, opts...)
  if err != nil {
  	fmt.Println("err: ", err)
  }
  ne.Close()
}

func main() {
  for i := 0; i < 5; i++ {
  	run()
  }
}

Start redis:

$ docker run -p 6379:6379 redis/redis-stack-server:latest

Before:

$ go run .
0xc000987d10, [0xc001424fc8]
0xc000987d10, [0xc001424fc8 0xc000a82fc8]
0xc000987d10, [0xc001424fc8 0xc000a82fc8 0xc00979c248]
0xc000987d10, [0xc001424fc8 0xc000a82fc8 0xc00979c248 0xc000a83448]
0xc000987d10, [0xc001424fc8 0xc000a82fc8 0xc00979c248 0xc000a83448 0xc00979c908]

After:

$ go run .
0xc000c8e190, [0xc0009eafc8]
0xc000d84500, [0xc0009eb448]
0xc001004460, [0xc002e1e248]
0xc000c8f310, [0xc002e1eb48]
0xc000c8fa90, [0xc002e1e6c8]

[tarunKoyalwar]

lgtm !

Awesome ! looks like we now know why we were still seeing template references even if we take mem profiles at end of execution

@Mzack9999 , along with template cache in templates package , we also have another internal cache in parsers package , included that as well and abstracted global cache register/purge via config

[Mzack9999]

I'll open a follow up PR as the design appears to be broken. The global cache should contain only templates in their most abstract and general representation, while the "compilation" should happen lazily and be usable independently by various runners without cross-references.