Automated testing

[dharabor]

• We need to add a test program, which executes unit, integration and system tests. For a first pass, we will import back the original test cases from the old bitbucket version of warthog.
• We also need to create a "test" folder with copy into the repo a limited set of data for the tests (maps, scenarios). The test data can also be referred to in the example usage documentation. Suggest CSC2F, random and arena2 + associated scenarios, as a start.
• We need to add README documentation that directs the user to run the tests, to make sure everything works.
• In the "tests" folder, we need documentation file (MOREDATA.md?) which directs the user to the SPL benchmark repo, where lots of maps and problem instances can be found.

[dharabor]

Once all the above is done, suggest a new discussion issue to talk about the testing strategy for warthog-core moving forward; i.e., which things we will write unit tests for, which things we will write integration tests for and which will just be system tests.

Another longer-term goal is CI/CD integration; run the tests as a post-commit hook.

[heavenfall]

Created first unit test for new bittable. #29
Has tests folder. Uses cache2. Enable BUILD_TESTING in cmake.