Application.Run<T> is broken by not calling Init before initializing T.

[BDisp]

Describe the bug
When a Toplevel is created, it must already have all the Application configuration loaded so that it can be used by any loaded derived Toplevel. Then Application.Run<T>() must call Application.Init() before initialize the T.
This is only possible by two ways:

1. Using Application.Init() first
2. Using Application.Run() or Application.Run<T>()

The Application.Run(new(Toplevel)) must always call Application.Init() first because the new(Toplevel) may be a derived class that is possible using Application static properties that is only available after the Application.Init was called

To Reproduce
Steps to reproduce the behavior:

1. Run the 'Example' project
2. See that the ExampleWindow configuration isn't been used (ColorSheme, Application.QuitKey)

Expected behavior
The ColorSheme used should be White/Blue and Ctrl+Q

Screenshots
Actual:

Expected:

Additional context
v2_develop branch