prog: better call-to-call priority calculation

The call priorities calculation is quite basic: https://github.com/google/syzkaller/blob/master/prog/prio.go Some things to improve:

Static priorities for call pairs should account for resource direction. For example, open produces an fd, write uses an fd, so it makes sense to add write after open, but not the other way around.
Dynamic priorities for call pairs should account for before/after. For example, setsockopt is only interesting after socket, but not the other way around.
The weights for resource usage may need tuning.
When we insert a call, we choose a "base" call to use in priority selection of the new call: https://github.com/google/syzkaller/blob/040fda588472da50749a3f605e183ad5c02104f4/prog/rand.go#L473. If we insert a call into the middle of the program during mutation, we should choose the "base" call only from the call before the insertion program (not all calls in the program).

google / syzkaller