Fix callMethodOnDumper treating false config values as no-argument calls

[isaackaara]

What this fixes

When a dump config option is set to false, callMethodOnDumper was calling the method with no arguments because of the falsy check:

if (! $methodValue) {
    $dbDumper->$methodName();  // setSkipSsl() defaults to true
    return $dbDumper;
}

The issue is setSkipSsl() (and similar methods on DbDumper) have bool $param = true as the default parameter. So calling them with no arguments sets the value to true even when the config explicitly says false.

Reproduction:

// config/database.php
'dump' => [
    'skip_ssl' => false,
],

The dumper ends up with skipSsl = true because:

1. Line 51 correctly sets it to false
2. processExtraDumpParameters then processes the dump config again, hitting skip_ssl => false
3. callMethodOnDumper sees !false === true and calls setSkipSsl() with no args → defaults to true

Fix

Change the check from ! $methodValue to $methodValue === null. Flag-style options (like use_single_transaction) produce a null $methodValue from processExtraDumpParameters, so those still call the no-argument form. Falsy values like false and 0 are now passed through correctly.

// Before
if (! $methodValue) {

// After
if ($methodValue === null) {

Test added

Added a test that confirms skip_ssl => false in the dump config results in skipSsl being false on the dumper.

Relates to: #1946

[freekmurze]

Thanks for the fix and the clear write-up, @isaackaara!