Revisit order of registration for RegisterGlobalTearDown()

[Suremaker]

Description

As per https://github.com/LightBDD/LightBDD/wiki/SetUp-and-TearDown#registerglobalsetup RegisterGlobalTearDown() are executed in the reverse order to the SetUps to ensure the most outer activities (ones that have been setup first) are torn down as last one.
While this behavior is expected, it forces calling RegisterGlobalTearDown() as a very first entry if it is expected the tear down to be called as the very last one - which can be counterintuitive.

As part of this ticket it should be explored on how to allow registering setups and teardowns in the natural order while still maintaining proper order of the execution.

Progress

• Feature is implemented,
• Ensured backward-compatibility,
• Ensured good debugging experience