Reduce casts of traits that are already known to be IDisabledTraits

[abcdefg30]

Exts.IsTraitEnabled(this T trait) uses trait is IDisabledTrait disabledTrait (and thus FirstEnabledTraitOrDefault does as well). That is not necessary if we already know that T is an IDisabledTrait.

I introduced a new FirstEnabledConditionalTraitOrDefault that directly checks where T : IDisabledTrait in the signature and replaced unnecessary usages of Exts.IsTraitEnabled with direct calls to IsTraitDisabled.

[anvilvapre]

I did a separate experiment in the past to determine the impact of the cast.

I tried to Func<T extends ConditionalTrait>() also avoiding the need to cast, but it did not give an obvious performance benifit.

I would be in favor of a trait base class that would have a flags fields that would indicate for any trait if it was enabled, paused perhaps timed. For non conditional traits it would always be true.

Also because more and more traits seem to become conditional, because the game developers want more flexibility to enable traits.

[PunkPun]

Changelog