Clarifying vulnerability payment amounts and categories

Created by: chayim

This pull request clarifies our vulnerability payment amounts, based on category, in descending order of payment amount.

My approach to outcomes stems from the relative value of the vulnerability from our point of view. For example, a user reading or writing to another user's code, encompasses the variety of data loss possibilities, as well as modifying customer code. That should be the holy grail.

We still want to encourage reports on misconfigurations that could lead to a security event; the early we know about a possibility, the earlier we can address it . As such that is the single, non-user focused outcome in this list.