Ransomware config UI description

[mssalvatore]

What does this PR do?

Adds a description and link to documentation to the ransomware configuration UI.

Issue #1239

PR Checklist

• Have you added an explanation of what your changes do and why you'd like to include them?
• Is the TravisCI build passing?
• Was the CHANGELOG.md updated to reflect the changes?
• Was the documentation framework updated to reflect the changes?

Testing Checklist

• Added relevant unit tests?
• Have you successfully tested your changes locally?

  See screenshot

• If applicable, add screenshots or log transcripts of the feature working

Screenshots

[codecov]

Codecov Report

Merging #1286 (e1263ec) into develop (f698c88) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop    #1286   +/-   ##
========================================
  Coverage    30.68%   30.68%           
========================================
  Files          449      449           
  Lines        13470    13470           
========================================
  Hits          4133     4133           
  Misses        9337     9337           

Impacted Files	Coverage Δ
...key_island/cc/services/config_schema/ransomware.py	100.00% <ø> (ø)

---

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 f698c88...e1263ec. Read the comment docs.

[VakarisZ]

I wonder if this is not excessive info since the user is in the ransomware tab under the ransomware title, so it should be obvious that he's configuring ransomware simulation here. The fact that it's safe to run in production environment can be said about almost every field in configuration and monkey in general. The only thing I see as a must is a link to the documentation hub.

[mssalvatore]

I've done some thinking about it. I haven't really been able to come up with a better short description of what these configuration options are. I think it's worth the note about it being "safe", so people don't panic when they see "ransomware."

As we continue to work on this capability, we can revisit this.

[VakarisZ]

Approved, but it's worth the extra 5mins of thought to make sure that the config is both readable and intuitive without being a burden to go through.