Clarify satisfaction of OpenMP-style dependencies in RFC 26

[jameshcorbett]

The OpenMP-style dependencies introduced in RFC 26 don't specify how they are satisfied---whether it is after a job enters state RUN or INACTIVE or after the job enters state INACTIVE with a successful result. It would be great if the satisfaction could be customized, like:

- type: inout
  scope: user
  scheme: string
  value: foo
  satisfied: afterany