Fix: Rely on Laravel's default job retry settings for Imports/Exports

[ahinkle]

Description

This PR addresses an issue with the default retry behavior for failed imports, which can lead to unintended costs and resource usage. Specifically, the default behavior allows a bad import to continuously retry for 24 hours, potentially resulting in increased expenses due to services like AWS SQS and exception logging.

While the 24-hour retry window was designed to account for temporary issues like a database outage, it is more common for failures to result from code bugs or invalid data. Reducing the retry duration prevents these issues from escalating into excessive costs while still allowing jobs to retry a reasonable number of times.

We retain the existing method for those who prefer it while updating the default to align with your application (or Laravel's) defaults.

Fixes #13113 , #10816

Functional changes

• Code style has been fixed by running the composer cs command.
• Changes have been tested to not break existing functionality.
• Documentation is up-to-date.