pgsql: Fix pg_dump's handling of event triggers.

Fix pg_dump's handling of event triggers.

pg_dump with the --clean option failed to emit DROP EVENT TRIGGER
commands for event triggers. In a closely related oversight,
it also did not emit ALTER OWNER commands for event triggers.
Since only superusers can create event triggers, the latter oversight
is of little practical consequence ... but if we're going to record
an owner for event triggers, then surely pg_dump should preserve it.

Per complaint from Greg Atkins. Back-patch to 9.3 where event triggers
were introduced.

Discussion: https://postgr.es/m/[email protected]

Branch
------
REL9_6_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/82ebda7fffac8f4c796ef7d36d377bebca620528

Modified Files
--------------
src/bin/pg_dump/pg_backup_archiver.c | 6 ++++--
src/bin/pg_dump/pg_dump.c | 14 ++++++++++++--
src/bin/pg_dump/t/002_pg_dump.pl | 16 ++++++++--------
3 files changed, 24 insertions(+), 12 deletions(-)