[Suggestion] Why do you still use travis and not GitHub actions?

Hi there,

Full disclaimer, this is me tutting my own horn since I did develop the GitHub Action [setup-lazarus](https://github.com/gcarreno/setup-lazarus).

Are you doing anything so special that can only be done by Travis?

If not, take a look at these(maybe it has enough to get you unstuck from travis.com):
- [setup-lazarus](https://github.com/gcarreno/setup-lazarus) - GitHub action to install Lazarus+FPC and some, still incomplete, support for OPM packages
- [lazarus-with-github-actions](https://github.com/gcarreno/lazarus-with-github-actions) - The simplest of examples on how to use the `setup-lazarus` GitHub action.

Cheers,
Gus

Review the repository's existing Travis setup, then compare the linked setup-lazarus and lazarus-with-github-actions examples. Done would require an agreed decision on whether GitHub Actions supports this project and a defined migration scope, which the issue does not currently specify.

Written by the indexing model from the issue text.