Improvement: Bazel as build, test and integration tool

[ltekieli]

PR: #9

Bazel is the build/test infrastructure of choice for the Score project. Overall integration and
build should be realized using available rule sets or custom rules developed for the project.
This means that the following should be integrated with bazel:

• code build
• documentation build
• test runs
• binary runs
• external tooling

Running external tooling outside of Bazel should be limited as much as possible, in order to
streamline the development with simple bazel {build,test,run} command, across multiple
repositories and multiple languages.

All dependencies should be managed thru mechanism available in Bazel. Dependency to host system
should be limited as much as possible.

Each repository should register an entry in the bazel-registry for dependency management between
different modules.

High level integration dependency

Repositories:

• bazel-registry (implicit dependency, stores version of all modules)
• process (process description)
• score (requirements and architecture)
• reference-integration
• module1
• module2
• ...

References:

• Bazel: https://bazel.build/
• Bazel modules: https://bazel.build/external/module
• Bazel registries: https://bazel.build/external/registry