Add a report/log option to filesystem exceptions without throwing

[lotharthesavior]

This PR introduces a new feature that allows users to configure whether filesystem operation errors should be logged without throwing exceptions.

Key Changes:

• Added a report configuration option to the disk configuration in filesystems.php.
• Enhanced the Filesystem Adapter to support logging errors.
• Users can now:
  • To throw exceptions by setting "throw" => true in their disk configuration.
• With this PR, Users will be able to:
  • To log errors without throwing exceptions by setting "report" => true.

Use Case:

This feature provides flexibility for users who want to monitor filesystem errors through logs instead of disrupting their application flow with exceptions. It’s particularly useful for non-critical operations where logging errors is sufficient or for monitoring/auditing purposes.

Example Configuration:

'disks' => [
    'local' => [
        'driver' => 'local',
        'root' => storage_path('app'),
        'throw' => false, // Suppress exceptions
        'report' => true,    // Enable error logging
    ],
],

Impact:

• If throw is true, exceptions will still be thrown.
• If throw is false and report is true, errors will be logged.
• If neither is set, the current behavior remains unchanged.

This change maintains backward compatibility while providing more granular error-handling options for filesystem operations.

[taylorotwell]

The report_if helper is defined in the framework and not in the support Composer package, so this would break for anyone using illuminate/filesystem without the framework.

[lotharthesavior]

That’s great! I hadn’t noticed that dependency issue before. I fixed it by using the exception handler from the application container only if it's available. If it’s not, the code simply does nothing. This solution also preserves the dependency injection strategy for the adapter.

As for the code style, it’s not passing, but I read in the contribution docs that it’s not required at the code review stage since it’s automatically handled at the merge.