Finish porting test suite to Bazel [BUILD-311]

[krisukox]

Description

@swift-nav/devinfra

This PR adds the following bazel targets:

• sbp-v4-test
• sbp-cpp-v4-test
• sbp-string-test
• sbp-cpp-legacy-test

In the sbp-cpp-legacy-test, SbpStdioTest.ReadsSbpFiles and SbpStdioTest.WritesToSbpFiles targets have undefined behavior. Assignment of msg to payload in the MsgObsHandler::handle_sbp_msg function causes this issue.
It works better with gcc-11 but still, these two testcases shouldn't be run together. In order to run all the test cases:
CC=gcc-11 CXX=g++-11 bazel test --test_output=all //c:all --test_arg=--gtest_filter=-SbpStdioTest.WritesToSbpFiles
CC=gcc-11 CXX=g++-11 bazel test --test_output=all //c:sbp-cpp-legacy-test --test_arg=--gtest_filter=SbpStdioTest.WritesToSbpFiles

JIRA Reference

https://swift-nav.atlassian.net/browse/BUILD-311

[jungleraptor]

I'm going to chalk the test failure up to the bazel submodule not being public. Not super concerning since we're just merging into a branch.

I tested locally without your command line flags and I didn't run into any errors with either gcc-11 or clang-14.

[jungleraptor]

Suggested change

	],
	],
	tags = ["exclusive"],

This attribute will make it so that the test run serially after the other tests. I don't think it's as granular as making the individual tests themselves run in serial but it might be worth a shot.

[jungleraptor]

Doc here: https://bazel.build/reference/be/common-definitions#common-attributes-tests

[krisukox]

Today, even when I run all of the tests at once, it works for me with gcc-11.
Clang-14 still doesn't work, even with the "exclusive" tag.
The behavior is so unpredictable. I will create a ticket about it.