[11.x] Fix schema names on DatabaseTruncation trait (PostgreSQL and SQLServer)

[hafezdivandari]

Fixes #53745

Unlike migrate:fresh, db:wipe commands, and RefreshDatabase trait, the DatabaseTruncation trait does not handle schema names on SQLServer and PostgreSQL and doesn't respect search_path on PostgreSQL.

This PR does:

• Fix DatabaseTruncation trait to support schema names (SQLServer and PostgreSQL).
• Fix DatabaseTruncation trait to respect search_path config of the DB connection (PostgreSQL).
• Handle prefix config better on DatabaseTruncation trait.
• Add tests for DatabaseTruncation trait.
• Optimize Schema::dropAllTables(), Schema::dropAllViews(), and Schema::dropAllTypes() methods on the PostgreSQL schema builder: No need to escape schema names when comparing values, because Schema::getSchemas() and Schema::getTables() return unescaped values.

Example

Refer to DatabaseTruncation docs.

use DatabaseTruncation;

protected $tablesToTruncate = ['foo', 'private.bar']; // Truncates tables named "foo" on all schemas and "bar" table on "private" schema only.
protected $exceptTables = ['foo', 'private.bar'];     // Truncates all tables except any tables named "foo" on any schema, "bar" table on "private" schema.

You can also define these properties based on connection names:

use DatabaseTruncation;

protected $tablesToTruncate = [
    'mysql' => ['foo'],                // Truncates "foo" table when using "mysql" connection.
    'pgsql' => ['foo', 'private.bar'], // Truncates tables named "foo" on all schemas and "bar" table on "private" schema only when using "pgsql" connection.
];

protected $exceptTables = [
    'mysql' => ['foo'],                // Truncates all tables except "foo" table when using "mysql" connection.
    'pgsql' => ['foo', 'private.bar'], // Truncates all tables except any tables named "foo" on any schema, "bar" table on "private" schema when using "pgsql" connection.
];

Note: migrations table (on all schemas) is always ignored, and never get truncated using this trait.

[github-actions]

Thanks for submitting a PR!

Note that draft PR's are not reviewed. If you would like a review, please mark your pull request as ready for review in the GitHub user interface.

Pull requests that are abandoned in draft may be closed due to inactivity.

[taylorotwell]

Hi @hafezdivandari - can you fix the conflict and mark as ready for review?

[hafezdivandari]

Hi @taylorotwell it's ready.