This PR adds three pipelines to the repo, watching push and pull request events:

1. Build with Autotools (build_test_autotools.yml).
2. Build with CMake (build_test_cmake.yml).
3. Build Visual Studio Solution (build_test_sln.yml).

They make use of the integrated GitHub actions.

As the pipelines were being developed, some "bugs" were catched:

• A copy of Except.h was missing for WIN32 builds from cmake/QuickfixPrebuildSetup.cmake.
• DataDictionaryTestCase is buggy on Windows.
• resetBeforeAndAfterWithTestFileManager fixture from FileStoreTestCase is also buggy on Windows.

So a #ifndef _MSC_VER was added to take resetBeforeAndAfterWithTestFileManager out of the Windows compilation and the entries for DataDictionaryTestCase were commented out from src/CMakeLists.txt and from src/test_unit_vs15.vcxproj.

However, #280 fixes the issue with DataDictionaryTestCase, as it's possible to check by merging the present PR with that, reversing the last commit from the present PR and waiting for the tests to complete.

I understand that there's already a CI with Travis, but the present PR covers a more complete range of configurations. The Autotools pipeline runs on Linux and macOS; the CMake one, on Windows, Linux and macOS. The Visual Studio pipeline is the only one that covers only Windows runs.

As to configurations, the CMake pipeline covers debug and release, but do not touch architecture. The Visual Studio is the most complete in this regard, as it covers debug and release for the Win32 and Mixed Platforms architectures (those being the ones that make sense to build from quickfix_vs15.sln). The Autotools pipeline also do not touch on architecture and covers only release.

When it is possible the pipelines cover building and the three kinds of testing present - at, pt and ut. I think they stood for "Acceptance Tests", "Performance Tests" and "Unit Tests". Although it can be easily implemented, there are no tests for macOS. Also, the acceptance tests are set to be performed only for release builds triggered by pull requests. Performance tests also run only for release builds (but do so for both push and pull requests). Unit tests run always (except for macOS, as said earlier).

The Autotools pipeline just runs a make check after the build and then cats test/test-suite.log. The same actions as the ones done by Travis.

The only solution being used by the Visual Studio pipeline is quickfix_vs15.sln for GitHub's test runners only come with Visual Studio 2019 anyway. It was necessary to pass command line arguments to msbuild to force it to use the installed versions of PlatformToolset and WindowsTargetPlatformVersion:

If there's interest in merging this PR, I can address any issues that may arise.