Using throw config of filesystem disks when faking

[emulgeator]

Problem

When production code initializes a storage instance, it relies on the filesystem configuration, which includes a crucial setting called throw. Enabling throw removes the need for additional checks in the code to verify whether file operations succeeded, as the exceptions themselves provide that information. Moreover, production code often depends heavily on the exceptions thrown.

However, the Storage::fake() method, by default, creates a storage instance where errors do not trigger exceptions. To align the test environment with production behavior, you must explicitly set the throw configuration to true each time. Forgetting to do so can lead to issues, including false positives in tests.

With this update, the Storage faker will now respect the configuration to set the throw value, though it can still be manually overridden.

Behavior Before the Change

• throw always defaulted to false, regardless of the configuration.
• throw could be set to true via the $config parameter.

Behavior After the Change

• throw defaults to false if not specified in the configuration.
• If present, the throw setting is retrieved from the configuration.
• throw can still be explicitly set to true via the $config parameter.

[taylorotwell]

Please update the PR to include the proper docblocks as used throughout the rest of the framework. Please mark as ready for review when the requested changes have been made. Thanks!