v1.1.0: Improved ArangoDB integration

It was a little bit of back and forth to get the backup and restore for ArangoDB working on all platforms. Some permission issues for the arangorestore command caused some permission denied issues for the tests in Github Actions. Took a while to figure out the root cause (The fix is a chmod appended to the arangodumpcommand setting the permissions for the arangodb-backup directory). Thanks to @rfay for all the help and patience as well the introduction to tmate for debugging Github Actions and also thanks to @rocketeerbkw for the discussions during Drupal Dojo Austin and for the idea with applying the chmod command to the arangodb-backup folder in the web container instead of the arangodb container or volumes in the previous attempts. The following changes got introduced with the current release:

• The command arangodump got added. With ddev arangodump the ArangoDB database is save to .ddev/arangodb-backup.
• The command arangorestoregot added. With ddev arangorestore the ArangoDB database dump is restored from .ddev/arangodb-backup.
• The `spidergram.config.yaml got updated. The authentication section for arango got removed since it is no-auth anyway and the url updated to https.
• Port 8529 gets exposed to https in docker-compose.arangodb.yaml now as well and each request is forwarded to https. And the DDEV project and config folders get added as bind mounts.
• The project_files section in the install.yamlgot updated accordingly adding the arangodump and arangorestore commands.
• test.bats has been extended with tests to check the functionality of arangodump and arangorestore