Add AUDIT and POLICY to EntityType enum

[timopollmeier]

What:
The types AUDIT and POLICY are added to the EntityType enum and
the functions using them are updated to change them to TASK and
SCAN_CONFIG internally.

Why:
This allows using these compliance types in commands that distinguish
them from TASK and SCAN_CONFIG.
One such command will be GET_AGGREGATES where it will determine
what the usage_type option is set to in the GMP command.
The new types will be translated to TASK and SCAN_CONFIG for the GMP
commands.

How:
Tested by running a test script that uses the affected function with new entity types:
https://gist.github.com/timopollmeier/d6d45c832e49771b73e0b94d8b94daaa

Checklist:

• Tests
• CHANGELOG Entry
• Documentation

[codecov]

Codecov Report

Merging #353 (6cb0a1a) into master (9d0301f) will increase coverage by 0.07%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #353      +/-   ##
==========================================
+ Coverage   97.51%   97.58%   +0.07%     
==========================================
  Files          20       20              
  Lines        4311     4438     +127     
==========================================
+ Hits         4204     4331     +127     
  Misses        107      107              

Impacted Files	Coverage Δ
gvm/protocols/gmpv208/types.py	100.00% <100.00%> (ø)
gvm/protocols/gmpv9/gmpv9.py	98.21% <100.00%> (+0.57%)	⬆️
gvm/protocols/gmpv9/types.py	97.18% <100.00%> (+0.02%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9d0301f...6cb0a1a. Read the comment docs.

[y0urself]

You somehow also added create/modify permission/tags ... is that intended?

[timopollmeier]

You somehow also added create/modify permission/tags ... is that intended?

Yes, I added new versions of those functions that translate AUDIT into TASK and POLICY into SCAN_CONFIG because gvmd does not recognize the compliance types as valid resource/entity types.
Maybe there's a way to just call the old version with modified parameters but I don't know how well this would work
and if we want these kinds of dependencies between protocol versions.

[y0urself]

You need to provide tests for the new functions and Types.