Do not dump Babelfish initialize user

[rishabhtanwar29]

Description

When Babelfish initialize user is same between source and target servers
for dump/restore, the restore throws errors like "role ... already exists" and
"duplicate key value violates unique constraint..." etc while inserting catalog
entry for initialize user in babelfish_authid_login_ext catalog. These errors are
actually expected and makes sense as we know the user do already exists on
the target server but the whole restore gets rolled back in case the restore
process has been made transactional (--single-transaction option is used)
and there is no way for a user to fix this manually.

To overcome the above issue, the engine commit implements the logic to skip
dumping Babelfish initialize user as well as the "owner" column of
sys.babelfish_sysdatabases catalog table.

This commit implements logic to re-populate "owner" column of
sys.babelfish_sysdatabases catalog table during restore with the owner of
current database (which is going to be initialize user of target Babelfish database).

Test changes:

• Updated github dump/restore action to take two more options as input:
  1. dump-data-as: Dump table data using COPY or INSERT
  2. dump-format: Dump format (plain/custom/tar/directory)
• Updated dump-restore configurations to test all four dump formats and
  both data formats.
• Enabled --single-transaction option for restore so that any error during restore
  would result in restore getting rolledback and failed.
• Added TAP test coverage for pg_restore.
• Fixed BABEL-1206-vu-prepare test to insert valid data into varchar column.

Task: BABEL-4404
Signed-off-by: Rishabh Tanwar [email protected]

Engine PR: babelfish-for-postgresql/postgresql_modified_for_babelfish#216

Test Scenarios Covered

• Use case based -

• Boundary conditions -

• Arbitrary inputs -

• Negative test cases -

• Minor version upgrade tests -

• Major version upgrade tests -

• Performance tests -

• Tooling impact -

• Client tests -

Check List

• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.

For more information on following Developer Certificate of Origin and signing off your commits, please check here.