Fixed #16217: added skip_ssl on database dump config

[ntaylor-86]

fixes #16217

Recently ran into the same issue is as #16217

Looked up the docs for spatie/laravel-backup https://github.com/spatie/laravel-backup

And found there was a skip_ssl value that could be set in the config/database.php - https://github.com/spatie/laravel-backup/blob/dd810a2edae269392b93149d622930c5f916f599/docs/installation-and-setup.md?plain=1#L417

Manually tested setting the skip_ssl value to true in my docker containers config file, then I was able to successfully Generate a Backup manually from the UI.

[welcome]

💖 Thanks for this pull request! 💖

We use semantic commit messages to streamline the release process and easily generate changelogs between versions. Before your pull request can be merged, you should update your pull request title to start with a semantic prefix if it doesn't have one already.

Examples of commit messages with semantic prefixes:

• Fixed #<issue number>: don't overwrite prevent_default if default wasn't prevented
• Added #<issue number>: add checkout functionality to assets
• Improved Asset Checkout: use new notification method for checkout

Things that will help get your PR across the finish line:

• Document any user-facing changes you've made.
• Include tests when adding/changing behavior.
• Include screenshots and animated GIFs whenever possible.

We get a lot of pull requests on this repo, so please be patient and we will get back to you as soon as we can.

[what-the-diff]

PR Summary

• Introduction of a New Environment Variable for Database Operations
  The team introduced a new environment variable, namely DB_DUMP_SKIP_SSL in the .env.docker file. This allows us to bypass any SSL-related challenges when dumping the database, providing us with a convenient escape route during tricky situations.

• Incorporation of the New Option in Database Configuration
  The config/database.php file is now updated to include the new 'skip_ssl' option within the database dump configuration. The best part is that if not specified, it defaults to false, i.e., it does not interfere with standard operations.

These changes improve our flexibility when dealing with database manipulations, enabling the system to operate smoothly even in unfavorable conditions related to SSL.