I was organizing the documentation on Discrete mode, and since the #89389 was invading the role of the Deterministic option and generating confusion, I have reorganized the behavior.

This causes #89163 to recur, but that is the intended behavior to ensure Deterministic option result consistency. So #89163 needs to be controlled by turning off the Deterministic option.

Adding the is_init flag used by Dominant and Recessive instead of init_use_continuous to solve the issue overall.

I remember conversing with reduz a bit about this at the beginning of 4.0, but the problem with #92127 in the first place is that the reset animation does not play when the blend amount is 0.

The workaround is to either apply the reset animation even if the blend amount is 0, or to use a flag to apply the reset animation only once. This PR will use the former for Force Continuous and the latter for Dominant and Recessive. This will make the Dominant mode reset occur only once, so the problem in #89163 should not recur.

However, that init flag may not be very stable, since it changes depending on the timing of cache deletion in the absence of Continuous tracks. If real stability is needed, the timing of applying the Discrete value itself would need to be changed, but at this stage that change is too large.

Now I make Recessive the default due to reevaluating the overall behavior.

In the past, we changed it once in #88492 because there was a problem with the Reset track taking precedence, but this should not be a problem now, and Recessive should be a better default because it does not have the flicker that can occur with Dominant, and it gives the same results as 3.x.

In there are two animations:

Force Continuous:

Dominant:

Recessive:

I would like to include this in beta1 as this changes the default value, also consider the consistency with the blog post godotengine/godot-website#851.

Thanks!