[CI] Move console checks from Travis to Github Actions

[TomasVotruba]

Follow up to #1916

[TomasVotruba]

Ready to merge ✔️

[TomasVotruba]

Thank you 👍

Btw, do you any questions or WTFs in your mind?
I want this transition to be clear and safe to you, so don't hesitate and ask about any single silly weird line you see.

[bobdenotter]

So far it seems straightforward! I suppose the "tricky" part will be Behat. It's the part that fails most often on Travis for dubious reasons, and if I recall correctly, it was also the most complex to get working.

Tomorrow @I-Valchev will be at work again, so i'm sure he'll chime in as well! :-)

[TomasVotruba]

That's great, I never worked with Behat so that should not be a problem ;)

I see some first complications - https://github.com/bolt/core/runs/1177089242

It might be caused by incorrect composer.json setup:

       "post-install-cmd": [
            "php bin/console extensions:configure --with-config",
            "@auto-scripts",
            "php bin/console bolt:info"
        ],
        "pre-package-uninstall": [
            "php bin/console extensions:configure --remove-services"
        ],
        "post-update-cmd": [
            "php bin/console extensions:configure",
            "@auto-scripts",
            "php bin/console bolt:info"
        ],
        "auto-scripts": {
            "cache:clear --no-warmup": "symfony-cmd",
            "assets:install --symlink --relative %PUBLIC_DIR%": "symfony-cmd"
        },

This is seems like a project composer.json, e.g symfony/demo or laravel/laravel

I've found these lines in bolt/project

Saying that, what are those needed for here?

[I-Valchev]

@TomasVotruba @bobdenotter Yes I also think it's pretty clear and understandable. Good to know that we have console colours by adding --ansi. Thanks Tomas!