GitHub CI

[osteel]

Description

This PR moves away from TravisCI and Scrutinizer in favour of GitHub actions.

Motivation and context

TravisCI is a bit less reliable now and the connection with Scrutinizer was always a bit clunky.

How has this been tested?

GitHub PR triggering the workflow.

Types of changes

What types of changes does your code introduce? Put an x in all the boxes that apply:

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• I have read the CONTRIBUTING document.
• My pull request addresses exactly one patch/feature.
• I have created a branch for this patch/feature.
• Each individual commit in the pull request is meaningful.
• I have added tests to cover my changes.
• If my change requires a change to the documentation, I have updated it accordingly.