Monolog Logger Compatibility Issue

### Steps to Fix

#### 1. **Update Dependencies**
Ensure all your dependencies, including `monolog/monolog`, are up to date to match the latest versions of `psr/log`. Run the following commands:

composer update monolog/monolog
composer update psr/log

After updating, check if the issue is resolved.

#### 2. **Check Compatibility**
Verify the version of Monolog and PSR Log being used:

– **PSR Log 3.x** requires Monolog 3.x.
– If your project uses PSR Log 3.x, ensure Monolog is also upgraded to version 3.x to avoid such compatibility issues.

Run:

composer show monolog/monolog psr/log

Check the versions in the output.

#### 3. **Downgrade PSR Log (if needed)**
If you cannot upgrade Monolog to version 3.x due to other dependencies, you may downgrade `psr/log` to version 1.x or 2.x, which are compatible with Monolog 2.x.

composer require psr/log:^2.0

#### 4. **Temporary Workaround (Not Recommended)**
If you cannot update your dependencies immediately, you can modify the `Logger` class in Monolog (not recommended for production). Update the `emergency` method signature in the `Logger.php` file:

public function emergency(Stringable|string $message, array $context = []): void
{
    $this->addRecord(Level::Emergency, (string) $message, $context);
}

However, **this approach is not advisable**, as any updates to Monolog will overwrite your changes. Updating your dependencies is the proper solution.

#### 5. **Clear Cache**
After making changes, clear your Composer autoload cache to ensure the updates are applied:

composer dump-autoload

Restart your PHP server, and the issue should be resolved.

### Correct Signature for `alert` Method
To align with `PsrLogLoggerInterface`, the `alert` method in the `MonologLogger` class should look like this:

public function alert(Stringable|string $message, array $context = []): void
{
    $this->addRecord(Level::Alert, (string) $message, $context);
}

### General Solution
As this problem likely applies to all logging methods (`emergency`, `alert`, `critical`, `error`, etc.), you should ensure that your version of Monolog matches the PSR Log version requirements. The proper solution is to update your dependencies:

#### 1. Update Monolog and PSR Log
Run the following commands to update the packages to compatible versions:

composer update monolog/monolog psr/log

Ensure that:
– **PSR Log

if (isset(self::RFC_5424_LEVELS[$level])) {
$level = self::RFC_5424_LEVELS[$level];
}

$level = static::toMonologLevel($level);
}

$this->addRecord($level, (string) $message, $context);
}

### Expected Changes
The `log` method in `PsrLogLoggerInterface` requires the `$message` parameter to be of type `Stringable|string`, and the method should return `void`. Your current `log` method may need adjustments to match this.

Here’s an updated version of your `log` method to align with `PsrLogLoggerInterface`:

public function log($level, Stringable|string $message, array $context = []): void
{
    if (!$level instanceof Level) {
        if (!is_string($level) && !is_int($level)) {
            throw new InvalidArgumentException('$level is expected to be a string, int or '.Level::class.' instance');
        }

        if (isset(self::RFC_5424_LEVELS[$level])) {
            $level = self::RFC_5424_LEVELS[$level];
        }

        $level = static::toMonologLevel($level);
    }

    $this->addRecord($level, (string) $message, $context);
}

### Key Changes:
1. **Method Signature**: The `$message` parameter is updated to be of type `Stringable|string`, which allows both strings and objects that implement the `__toString` method to be accepted.
2. **Return Type**: The method should now return `void`, which is the expected return type in `PsrLogLoggerInterface`.

### Additional Considerations
Ensure that your `Level` constants are correctly mapped and compatible with this update. If the `Level` class is a custom implementation, verify that it follows the necessary logging level definitions required by PSR-3.

### Solution Recap:
– **Update Monolog** to the latest version compatible with PSR-3 (if not already).
– **Ensure the correct method signature** for methods like `log`, `emergency`, `alert`, etc.
– If the method signature changes are not sufficient, updating your Monolog version or `psr/log` dependency should resolve this.

### After the Changes:
Once you’ve made the necessary changes, you can clear Composer's autoload cache and test your application to ensure that the logging methods now conform to the expected signatures.

composer dump-autoload