[12.x] Log: Add optional keys parameter to Log::withoutContext to remove selected context from future logs

[mattroylloyd]

Description

This PR adds an optional $keys parameter to the withoutContext method, allowing to selectively remove specific context keys from the logger instance.
When no keys are provided, existing behaviour is not changed - the method continues to clear all context as before.

Thanks to @slashequip for the inspiration 💜

// Clear all context (existing behavior)
Log::withoutContext();

// Remove specific context keys
Log::withoutContext(['post_id', 'comment_id']);

Benefits

• Provides more granular control over which context keys to remove, without needing to remove all context or update the context value to a null value.
• Allows context to be easily scoped to a specific operation, without impacting context added elsewhere in the lifecycle.
• Maintains backward compatibility with existing withoutContext usage

Example

The withoutContext method can now be used to remove specific context keys while preserving others:

class SyncPostWithPlatformAction
{
    public function handle(Post $post): void
    {
        // Add post context
        Log::withContext(['post_id' => $post->id, 'platform' => $post->platform]);

        Log::info('Fetching latest update from platform');

        // do work

        Log::info('Updated post with recent platform changes');
        
        // Removes only the additional context added for the duration of this action, preserving other
        // context added during the whole process, e.g. 'job', 'request_id', 'user_id', etc.
        Log::withoutContext(['post_id', 'platform']);
    }
}

Why?

We want to lean more into using withContext, but can end up polluting the context when using our actions within http requests, queued jobs, commands. It means we usually end up repeating the context throughout more complex actions in order to not pollute other logs created from outside of the action.

[AhmedAlaa4611]

Has it been documented yet?