Move CI to GitHub Actions

[geerlingguy]

Travis CI rather abruptly ended its generous open source build plans, and Drupal VM has been without any active CI for almost a month now.

I should rectify that, by moving the existing CI workflows over to GitHub Actions.

I'll maybe also take this opportunity to clean things up a bit and maybe switch to Molecule, if that's an easy transition. If it turns out to be too complicated, I'll drop that and just do a straight migration.

[geerlingguy]

Looks like it might not be so bad moving everything to GH Actions and Molecule at the same time. I might have to do a little extra work getting some of the extra testing steps incorporated, but this is going to make complexity go way down.

[geerlingguy]

Needing to fix some issues in Drush role, Ansible for Kubernetes, and Drupal role to get further on this :P

"It'll be quick," I said to myself earlier today... Here I am 6 hours later.

[geerlingguy]

Drat, now I'm running into the issue from my MySQL role:

TASK [geerlingguy.mysql : Ensure MySQL is started and enabled on boot.] ********
fatal: [instance]: FAILED! => {"changed": false, "msg": "Unable to start service mysql: Job for mariadb.service failed because a timeout was exceeded.\nSee \"systemctl status mariadb.service\" and \"journalctl -xe\" for details.\n"}

[geerlingguy]

Fixed by disabling AppArmor on debian builds: geerlingguy/ansible-role-mysql#422

[geerlingguy]

Follow-up issue: #2114