Handle script timeout as script preferences instead of server preference

[jjnicola]

What

Currently is sent to openvas as timeout.
Now is sent as as a script preference as param with ID 0 subelemet of the vt_single in the vt_selection.

[main branch] All related PRs:

• openvas: Store and get the script timeout as preference openvas-scanner#844 (comment)
• gvm-libs: Handle script timeout as script preference gvm-libs#581
• gvmd: Close SC-355 . Send the script timeout to the scanner as script preferences instead as server preference. gvmd#1670
• ospd-openvas: Handle script timeout as script preferences instead of server preference #509

Why:
To handle the timeout consistently as script preference between scanner and gvmd

How did you test it:
Set a custom timeout for a script and check that the timeout is accepted.What:
Handle script timeout as script preferences instead of server preference

Checklist:

• Tests
• PR merge commit message adjusted

[codecov]

Codecov Report

Merging #509 (c9f3ebf) into main (b8f9a7e) will decrease coverage by 0.08%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #509      +/-   ##
==========================================
- Coverage   80.25%   80.16%   -0.09%     
==========================================
  Files          10       10              
  Lines        1666     1649      -17     
==========================================
- Hits         1337     1322      -15     
+ Misses        329      327       -2     

Impacted Files	Coverage Δ
ospd_openvas/db.py	97.05% <ø> (ø)
ospd_openvas/nvticache.py	94.01% <100.00%> (+0.07%)	⬆️
ospd_openvas/preferencehandler.py	90.19% <100.00%> (+0.22%)	⬆️

---

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 b8f9a7e...c9f3ebf. Read the comment docs.