Added Makefile with bazel wrappers [BUILD-360]

[wwieclaw]

Description

@swift-nav/devinfra

Adding a Makefile into the c directory for commonly used bazel commands to make it easier for developers to start using bazel.

Added targets:

• do-all-unit-tests
• do-all-integration-tests
• clang-format-all-check
• clang-format-all
• clang-tidy-all-check
• do-code-coverage
• do-generate-coverage-report

I'm using aspects to run clang-format and clang-tidy on each file. You can see the setup in .bazelrc
I'm loading .clang-format configuration in .bazelrc

API compatibility

Doesn't break anything, it's just a new Makefile

JIRA Reference

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

[wwieclaw]

@silverjam @isaactorz using clang-format with bazel doesn't work for me here:

.clang-format:96:5: error: unknown key 'Delimiter'
  - Delimiter:       pb

Delimiter has been replaced with Delimiters in newer versions of clang and we are using clang-format 14 in bazel.

Is it okay for me to update the libsbp's config?

[jungleraptor]

@silverjam @isaactorz using clang-format with bazel doesn't work for me here:

.clang-format:96:5: error: unknown key 'Delimiter'
  - Delimiter:       pb

Delimiter has been replaced with Delimiters in newer versions of clang and we are using clang-format 14 in bazel.

Is it okay for me to update the libsbp's config?

I don't think so, that will break formatting in CI I'm pretty sure.

Several months ago now we went and updated all of the codebase to using clang-format-14 and clang-tidy-14 but we overlooked this repo because formatting is set up a little differently than the rest. We also need to update the formatter in the base image to get it going in CI.

Let's punt on enabling formatting w/ bazel in this project for right now.

[wwieclaw]

I removed clang-format related configuration to avoid any confusion

[jungleraptor]

lgtm