Update to latest YARA Forge release (2024-04-07)

[tstromberg]

As per the new makefile rule in #105

Contrary to the huge diff, there are only a few new rule additions:

+BINARYALERT_Hacktool_Windows_Cobaltstrike_Artifact_Exe
+ELASTIC_Linux_Exploit_Log4J_7Fc4D480
+ELASTIC_Linux_Trojan_Merlin_55Beddd3
+ELASTIC_Linux_Trojan_Xzbackdoor_74E87A9D
+RUSSIANPANDA_Win_Mal_Koi_Loader
+RUSSIANPANDA_Win_Mal_Koi_Loader_Decrypted
+RUSSIANPANDA_Win_Mal_Koistealer_PS

[cpanato]

there is some lint errors, can you take a look @tstromberg ?

[tstromberg]

It seems to be part of some woke linter I'm not familiar with:

 Running woke with reviewdog 🐶 ...
  reviewdog: This GitHub token doesn't have write permission of Review API [1], 
  so reviewdog will report results via logging command [2] and create annotations similar to
  github-pr-check reporter as a fallback.
  [1]: https://docs.github.com/en/actions/reference/events-that-trigger-workflows#pull_request_target, 
  [2]: https://help.github.com/en/actions/automating-your-workflow-with-github-actions/development-tools-for-github-actions#logging-commands
  reviewdog: Reporting results for "woke"
  Error: [woke] reported by reviewdog 🐶
  Warning:  `whitelist` may be insensitive, use `allowlist`, `inclusion list` instead
  
  Raw Output:
  Warning: ty/yara-rules-full.yar:8686:7: [warning] `whitelist` may be insensitive, use `allowlist`, `inclusion list` instead
  Error: [woke] reported by reviewdog 🐶
  Warning:  `whitelist` may be insensitive, use `allowlist`, `inclusion list` instead

This linter won't work well with third party code. I'll see if there is a way to turn it off for the third-party directory.

[cpanato]

I think we can add the .wokeignore and add the path there