[8.x] Add pg_dump --no-owner and --no-acl to avoid owner/permission issues

[rihardsgrislis]

Hey,

fcf175b changed PostgreSQL schema loading to use pg_restore but it fails when you dump schema on one computer and restore it on another (let's say one developer dumps schema, another one loads it) due to owner/permission issues (see below).
You can add --no-owner and --no-acl options to either pg_dump or pg_restore but I think it doesn't make sense to commit a schema with owners/permissions in the case (might be wrong, no problem to change - let me know).

Symfony\Component\Process\Exception\ProcessFailedException 

The command "PGPASSWORD=$LARAVEL_LOAD_PASSWORD pg_restore --host=$LARAVEL_LOAD_HOST --port=$LARAVEL_LOAD_PORT --username=$LARAVEL_LOAD_USER --dbname=$LARAVEL_LOAD_DATABASE $LARAVEL_LOAD_PATH" failed.

Exit Code: 1(General error)

Working directory: /Users/rihardssceredins/Code/api-diet

Output:
================

Error Output:
================
pg_restore: while PROCESSING TOC:
pg_restore: from TOC entry 8; 2615 415790 SCHEMA public janisozolins
pg_restore: error: could not execute query: ERROR:  schema "public" already exists
Command was: CREATE SCHEMA public;

pg_restore: error: could not execute query: ERROR:  role "janisozolins" does not exist
Command was: ALTER SCHEMA public OWNER TO janisozolins;

pg_restore: from TOC entry 420; 1255 415886 FUNCTION datediff(character varying, timestamp without time zone, timestamp without time zone) janisozolins
pg_restore: error: could not execute query: ERROR:  role "janisozolins" does not exist

[rihardsgrislis]

Setting those options on pg_restore would make sense to fix schema dump restoration for those who already upgraded to Laravel 8.8.0, but the release hasn't been marked as latest/release notes published. Let me know what option you think is best.