[FEATURE REQUEST] Merge java-deobfuscator

[OpticFusion1]

Is your feature request related to a problem? Please describe.
Currently the Anti-Malware is unable to detect obfuscation or deobfuscate jars, merging the deobfuscator will fix this.
It should be possible to deobfuscate and scan deobfuscated jars, however this should be under a --deobfuscate CLI argument so as to not spend unneeded time if false it should just log as "[INFO] Java.Obfuscator.ObfuscatorName.Variant" e.g Java.Obfuscator.Stringer.v3, Java.Obfuscator.Stringer.v3_1, or Java.Obfuscator.Stringer.v9

https://github.com/java-deobfuscator/deobfuscator/

Describe the solution you'd like
N/A

Describe alternatives you've considered
N/A

Additional context
N/A

[OpticFusion1]

Working on this, it's bound to bump of the file size a good bit.
Current File Size: 21.5 MB

[OpticFusion1]

Expanding on this, the scanner should work in 3 stages

Stage 1:
Check plugin jars for obfuscation and if --deobfuscate is set to true save the jar and a list of used obfuscation methods otherwise log as shown in the original message. How the information is stored depends on how to best complete Stage 2.

Stage 2:
If --deobfuscate is not true this case be skipped otherwise deobfuscate jars and save the deobfuscated jars to AntiMalware/deobfuscated/ created directory should contain the deobfuscated file and a text file with the original file path

Stage 3:
Scan if --deobfuscate is true, scan the deobfuscated jars first and if any malware is found log BOTH the deobfuscated jar as well as the original jar then scan the rest of the jars.

[OpticFusion1]

Merging java-deobfuscator bumps the size up to 32,9 MB a full implementation would of course bump it up even more

[OpticFusion1]

Could do a completely custom deobfuscator as well, it would go in optic_fusion1.antimalware.deobfuscator