[CI] unit testing in FreeBSD and OpenBSD systems

[alex-w]

Description

This pull request added support to build and run unit tests in FreeBSD and OpenBSD systems.

Important part of this PR is updated unit tests for JavaScripting (The deep investigation of test fails is needs for FreeBSD/Qt5 CI).

Type of change

• Housekeeping

[github-actions]

Great PR! Please pay attention to the following items before merging:

Files matching src/**/*.cpp:

• Are possibly unused includes removed?

This is an automatically generated QA checklist based on modified files.

[10110111]

Why do you disable ShowMySky here?

[alex-w]

Why do you disable ShowMySky here?

FreeBSD has binary package for Qt5-based ShowMySky only. At first attempt, building ShowMySky in FreeBSD/Qt6 was failed :(

Let's enable it again and please check the results.

[10110111]

make[2]: make[2]: don't know how to make _deps/showmysky-qt6-build/check. Stop

I guess this is because of the spaces in check version update target. Try using the latest master of CalcMySky, I've pushed a potential fix for this.

[alex-w]

OK.

NetBSD: no exist binary package of MesaLib for NetBSD 9.x and it's not possible to build it from source code (via pkgsrc) due limitations for VM, so, the critical dependency is missing - no OpenGL, no Stellarium.

DragonflyBSD: Stellarium built without ShowMySky and Lens Distortion Estimator plugin, because binary packages of dependencies for these features is too old. Building from source code is failing (probably GCC 8.4 is too old for it).

[alex-w]

OK.

Solaris: version 11.4 was released in 2018 and it has too old packages (cmake 3.9), so, I removed this CI

[alex-w]

@gzotti @10110111 please review the PR

[gzotti]

I wonder how many kWh per commit we are burning... And how much of that is just "install environment" before even compilation... :-o

[gzotti]

I see no problems now.

[10110111]

Some builds fail. Is it expected?

[10110111]

Why did you have to edit the tests in this PR?

[alex-w]

Some builds fail. Is it expected?

it's something wrong in memory with Qt5/QtScript - I didn't checked it in deep

[alex-w]

Why did you have to edit the tests in this PR?

wrong limits, so, some parts of tests never running before