Remove problematic SET statements from the developer database dump

[jonatanklosko]

Currently the database developer dump gives the following warning on production:

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.

The dump includes two problematic statements: SET @@GLOBAL.gtid_purged and SET @@SESSION.SQL_LOG_BIN, I guess that's been the case since we upgraded MySQL version. While loading the dump locally may work if the given database user has full permissions, it fails on the staging due to lack of the necessary permissions. Setting the option doesn't include these options, which correctly removes the warning and also omits the problematic SET statements, so I believe that's a reasonable thing to do.

@tussosedan please let me know if there's any reason we wouldn't want doing so =)

[tussosedan]

As these options have to do with replication, it seems safe to get rid of them for the dev dump. Thanks!