move logSessionCreation after session is initialized

[zhangxiang1993]

Description: Because the default CPUExecutionProvider is registered inside session initialization and SessionCreation Logger is inside model loading. So CPUExecutionProvider would be missed to be logged.

This change is to move Logging Session Creation after the session is initialized.

[skottmckay]

Description: Because the default CPUExecutionProvider is registered inside session initialization and SessionCreation Logger is inside model loading. So CPUExecutionProvider would be missed to be logged.

This change is to move Logging Session Creation after the session is initialized.

Can you clarify how moving the creation to later in the setup process (Initialize is called after Load) helps with something about the CPUExecutionProvider not being logged?

[zhangxiang1993]

Description: Because the default CPUExecutionProvider is registered inside session initialization and SessionCreation Logger is inside model loading. So CPUExecutionProvider would be missed to be logged.
This change is to move Logging Session Creation after the session is initialized.

Can you clarify how moving the creation to later in the setup process (Initialize is called after Load) helps with something about the CPUExecutionProvider not being logged?

1. We are logging the EPs registered in execution_providers_
2. Non-default execution providers will be registered before loader according to options, so logger inside loader is able to log EPs.
3. Default execution provider, CPUExectionProvider will be registered when session is initialized, which happens after the logging. So the EP info is lost for the logger inside the loader.

This change is to move the logger to the end of initialization so CPUEP is registered before logging.