fix: Removes flag resolving from Confidence child instances

[fabriziodemaria]

The plan is to enable this back once we have support for it in the caching layer.

[nickybondarenko]

Would removing Contextual not be a breaking change? I am not sure whether it's necessary to remove 🤔

[fabriziodemaria]

Answering here for @vahidlazio as well: the problem I found with Contextual is that withContext returns a Self, and if it's Confidence implementing such protocol the return type can only be Confidence (while we want ConfidenceEventSender instead)

[fabriziodemaria]

I don't think that removing Contextual is a breaking change, since final users never operate with such type directly: they either have a Confidence instance or a ConfidenceEventSender instance

[nickybondarenko]

I think my issue with this is that removing Contextual then means this structure doesn't align with Android/JS anymore.
Right, so since Confidence doesn't confirm to EventSender, it won't be able to return one when calling withContext. I think that makes sense 👍 We should document this somewhere, but that's not necessarily part of this PR

[fabriziodemaria]

I think my issue with this is that removing Contextual then means this structure doesn't align with Android/JS anymore.

True, I am also not very about that. But as long as this is internals, it's less of a problem and we can always change it without breaking backwards compat with final users

Right, so since Confidence doesn't confirm to EventSender, it won't be able to return one when calling withContext.

Even if it would conform to EventSender, it seems like the return type Self only accepts the type of the implementing class Confidence