Protocol checks using iteration to load data assets results in check payloads binding last item in iteration

[J-81]

This results in things like sample wise checks with data asset inclusive payloads to load the data asset associated with the last sample in the iteration for all samples.

What was intended was for the sample payload to load the data asset(s) associated with the sample in the current iteration.

Impact:

entity-wise checks were inappropriately supplying data assets from the last iteration for all entity instead of current iteration

In the current protocols this impacts:
Sample-wise checks

Visibility:

The evaluated payload is present the log and shows the improper data asset paths were loaded.

Solution:

ref: https://stackoverflow.com/a/10452866/16862353

Converting all lambda lines in protocol payloads from:

lambda: entity.data_assets["k"]
to
lambda entity=entity: entity.data_assets["k"]

This will ensure entity is dereferenced at lambda definition INSTEAD of dereferenced at lambda evaluation

[J-81]

Testing Fix:

Prior table example:

...

After fix table example: