Fix: Prevent Early Invocation of Write-PodeErrorLog in Console Setup

[mdaneri]

Issue Description

This pull request implements #1514

Currently, Pode attempts to invoke Write-PodeErrorLog inside a catch block during console setup:

catch {
    $_ | Write-PodeErrorLog
    $ctx.Server.Console.DisableTermination = $true
    $ctx.Server.Console.DisableConsoleInput = $true
    $ctx.Server.Console.Quiet = $true
    $ctx.Server.Console.ShowDivider = $false
}

However, this occurs before the logging subsystem is fully initialized, leading to potential issues with the new logging features introduced in #1387

Proposed Fix

• Added a check to ensure the session is running in a console-like environment and is not marked as a daemon before proceeding.
• Removed the invocation of Write-PodeErrorLog from this section to avoid premature logging.

Updated Code

# Check if the current session is running in a console-like environment and it's not marked as Daemon
if (Test-PodeHasConsole -and ! $Daemon) {
    try {
        if (! (Test-PodeIsISEHost)) {
            if (!$ctx.Server.Console.Quiet) {
                [System.Console]::CursorVisible = $false

                if ($ctx.Server.Console.ShowDivider) {
                    [Console]::OutputEncoding = [System.Text.Encoding]::UTF8
                }
            }
            if (Test-PodeIsConsoleHost) {
                [Console]::TreatControlCAsInput = $true
            }
        }
    }
    catch {
        $ctx.Server.Console.DisableTermination = $true
        $ctx.Server.Console.DisableConsoleInput = $true
        $ctx.Server.Console.Quiet = $true
        $ctx.Server.Console.ShowDivider = $false
    }
}

Justification

• Implements Write-PodeErrorLog` Called Before Log Subsystem Initialization in Console Setup #1514
• Ensures Pode does not attempt to write to logs before the logging subsystem is available.
• Preserves expected console behavior while handling errors gracefully.
• Avoids potential conflicts with new logging features.

Testing

• Verified that Pode initializes correctly without triggering premature logging errors.
• Confirmed that the console behavior remains consistent after an exception.