Enable data export via MySQL Workbench

[jan-meyer-1986]

To export data via MySQL Workbench, we need to grant more privileges to the guest user to preempt errors on the client side.

By granting no privileges (except SELECT), following errors occur during export attempts:

03:29:14 PM Dumping AdventureWorks2014 (Shift)
[...]
mysqldump: Error: 'Access denied; you need (at least one of) the PROCESS privilege(s) for this operation' when trying to dump tablespaces
mysqldump: Got error: 1044: Access denied for user 'testuser2'@'%' to database 'AdventureWorks2014' when doing LOCK TABLES
Operation failed with exitcode 2

[jan-meyer-1986]

When granting PROCESS privileg only:
03:33:38 PM Dumping AdventureWorks2014 (Shift)
[...]
mysqldump: Got error: 1044: Access denied for user 'testuser2'@'%' to database 'AdventureWorks2014' when doing LOCK TABLES
Operation failed with exitcode 2

[jan-meyer-1986]

WHen granting LOCK TABLES Privilege only:

For every table:
03:40:03 PM Dumping AdventureWorks2014 (SalesTerritory)
Running: mysqldump --defaults-file="/tmp/tmpyt4t5s4l/extraparams.cnf" --host=34.140.8.102 --port=3306 --default-character-set=utf8 --user=testuser2 --protocol=tcp --column-statistics=FALSE --skip-triggers "AdventureWorks2014" "SalesTerritory"
Warning: A partial dump from a server that has GTIDs will by default include the GTIDs of all transactions, even those that changed suppressed parts of the database. If you don't want to restore GTIDs, pass --set-gtid-purged=OFF. To make a complete dump, pass --all-databases --triggers --routines --events.
Warning: A dump from a server that has GTIDs enabled will by default include the GTIDs of all transactions, even those that were executed during its extraction and might not be represented in the dumped data. This might result in an inconsistent data dump.
In order to ensure a consistent backup of the database, pass --single-transaction or --lock-all-tables or --master-data.
mysqldump: Error: 'Access denied; you need (at least one of) the PROCESS privilege(s) for this operation' when trying to dump tablespaces

But tables are still downloaded

[jan-meyer-1986]

When granting PROCESS and LOCK TABLE:
For every table:
04:01:55 PM Dumping AdventureWorks2014 (ProductCategory)
Running: mysqldump --defaults-file="/tmp/tmpz1e65ifc/extraparams.cnf" --host=34.140.8.102 --port=3306 --default-character-set=utf8 --user=testuser2 --protocol=tcp --column-statistics=FALSE --skip-triggers "AdventureWorks2014" "ProductCategory"
Warning: A partial dump from a server that has GTIDs will by default include the GTIDs of all transactions, even those that changed suppressed parts of the database. If you don't want to restore GTIDs, pass --set-gtid-purged=OFF. To make a complete dump, pass --all-databases --triggers --routines --events.
Warning: A dump from a server that has GTIDs enabled will by default include the GTIDs of all transactions, even those that were executed during its extraction and might not be represented in the dumped data. This might result in an inconsistent data dump.
In order to ensure a consistent backup of the database, pass --single-transaction or --lock-all-tables or --master-data.

and all Tables are downloaded