[11.x] Avoids SQLiteConnection::__construct throwing exceptions

[nunomaduro]

In Laravel 11, the database driver is the default store for the cache. Sometimes, if the user chooses SQLite as the database driver, SQLite will be used for caching. Typically, when the user creates a fresh Laravel application, the database/database.sqlite file may not exist, which can cause issues when starting a fresh Laravel application (via laravel new) or even just executing php artisan in the console:

   Illuminate\Database\QueryException

  Database file at path [/Users/nunomaduro/Work/Code/laravel/database/database.sqlite] does not exist. Ensure this is an absolute path to the database. (Connection: sqlite, SQL: PRAGMA foreign_keys = ON;)

This pull request addresses the issue by effectively ignoring the error in the constructor. While this approach may seem simplistic, it is the safest solution for two reasons:

1. Users who directly access the PDO will still have the query (update) executed, ensuring no change in behavior.
2. Users who later access the database, such as through the cache (for example, using cache::get), will still encounter the "Database does not exist" error.