test: Introduce BRIL coverage and retroactively validate recent changes
In our CI, automated testing only validates the continued operability of the GMT, Calo and Passthrough processors (the latter through the multi-stream test).
The BRIL processor use case is not covered. An example test file, present in a P5 node, can be integrated into the framework once retrieved. If possible, the output should be validated. The MR !83 (merged) can serve as a reference to keep BRIL tests uniform with future CI testing in SCDAQ.
NOTE: upon resolution, the group should take the opportunity to retroactively test recent changes to the framework, particularly those that are not intended to alter BRIL functionality, e.g., !82 (merged), !79 (merged) and !75 (merged)