Add Github Workflow to check compilation in Windows, Ubuntu and MacOS (latest)

[prashanthr05]

As a consequence of adding workflows,

• Updated dependencies
• Windows compilation was fixed by minor modifications to CMakeLists.txt

Additionally,

• Updated Authors

[HosameldinMohamed]

For me it's ok!, I also saw from your fork the test is passing.

Maybe we add a status badge in the README file.

Like this (I put the link of your fork):

System	Continuous Integration Status
Linux/macOS/Windows

[HosameldinMohamed]

Only for me to understand, could you point me to a line where there's a potential math symbol error?

[prashanthr05]

If you search for "error" in this raw log of that specific job in the workflow, you will find the problem. The raw log can be accessed by pressing ... in this page https://github.com/prashanthr05/whole-body-estimators/runs/506436067?check_suite_focus=true

This was actually reported by @traversaro in #6 (comment)

[prashanthr05]

Clicking the raw log points to an expired url. It's better to go directly to the actions tab in the repository and check the status.

[prashanthr05]

Maybe we add a status badge in the README file.

How did you do that?

[HosameldinMohamed]

Maybe we add a status badge in the README file.

How did you do that?

I've copied it & modified from another working repo 😄 .

You can modify the link of the badge:

![GitHub Actions Status](https://github.com/prashanthr05/whole-body-estimators/workflows/C++%20CI%20Workflow/badge.svg) 

• The link of the repository until the directory workflows is the location of the ci.yml file.
• The phrase C++%20CI%20Workflow is the name in the top of the file ci.yml:

name: C++ CI Workflow

• The badge.svg stays the same.

[prashanthr05]

Then maybe we have to merge to devel and copy the badge of robotology remote rather than prashanthr05 fork?

[HosameldinMohamed]

Then maybe we have to merge to devel and copy the badge of robotology remote rather than prashanthr05 fork?

Yeah, we can do that.

[fjandrad]

Sorry for the delay, interesting work I could not have really reviewed it since I do not now these workflow things yet. But looking at the code was useful to start getting acquainted. Nice @prashanthr05 explanations and comments are quite clear.

[prashanthr05]

Actually, it was only a very slightly modified version of the workflow in iDynTree and bipedal-locomotion-controllers.