Establish preliminary build/pull request validation checks

[jphickey]

There are certain items that should be confirmed with every proposed change to bplib before merging that change. Currently the list of tests is rather small but helpful nonetheless:

• rbtest (a functional test focused solely on the red-black tree implementation that underpins other logic)
• bptest (a self-contained functional test app that creates passes a string though bundleization and unbundleization)

Both of these tests should be executed on every PR to avoid regressions.

Furthermore, additional build verification could also be added similar to the other CFS apps, to execute static analysis tools.

In the future, this would also run all coverage tests as well (but these do not yet exist for the current implementation of BPLib)

[jphickey]

As there are a number of workflows to be considered this can be split into it's constituent parts to be implemented individually:

• Documentation workflow (TBD)
• Code coverage workflow (builds source, runs code coverage tests, compiles results and checks for regressions)
• Static analysis workflow (runs cppcheck and/or other tools against source tree)
• Functional test workflow (runs tools classified as functional test)
• CodeQL workflow (TBD, used in CFE/CFS, similar to static analysis but a different cloud-based tool, may require licensing of some sort)
• Format/Whitespace check (TBD)

Adding these can all be separately considered and implemented and thus each should be a separate issue

[jphickey]

Added issues #182, #183, #184, #185, #186, and #187, which will replace this.