fix (defer): deferred fragment condition evaluation

[calvincestari]

Conditions on a deferred fragment were not correctly being evaluated during field collection. This meant that deferred fragments would always be collected into _deferredFragments regardless of any condition. It's now fixed and deferred fragments are not collected if the condition would evaluate to false meaning the deferred fragment should never be expected to be received.

[AnthonyMDev]

This behavior is still wrong I think. If the conditions evaluate to false, the fragment will still be executed, it just won't be deferred. We need to treat it as a non-deferred fragment in that case, not ignore it completely.

[calvincestari]

Yes, you're right. 🤦‍♂️

I'll correct this when I'm back on Monday.

[calvincestari]

@AnthonyMDev this is now fixed with an additional test to ensure that a missingValue error is thrown during execution if the deferred data is not present with a false condition.

[AnthonyMDev]

Looks good now! Minor suggestions on the implementation, but the functionality is correct.