Currently continuation chains are being resolved with a call stack based approach. This has a couple consequences:

• Challenging callback destructor ordering semantics which need to be individually addressed in SERVER-66126
• Large stacks leading to stack overflows

Currently, the benefit that we get from the stack based resolution is some extra context in dumps (only with non-executor continuations on non-ready futures). Before committing to this task, it's worth considering whether that benefit is worth preserving, and it's worth looking into improvements that can be made to debugability in all cases.