Execution records for script plugin listeners are stored and fetched under different keys

When persisting or retrieving the results of listener executions, in both cases the key used is derived ultimately from the parameters map of the listener via hashing. When the listener comes from a script plugin, however, the map is slightly different between the two cases and thus the hashed keys are entirely different, so ScriptRunner fails to find the records which it had previously stored.

The way this manifests to the end user is that they always see "Has not run yet" next to plugin-provided listeners even when that isn't the case.