Improvement: Nightly Module Testing

> [!IMPORTANT]
> Make sure to link this issue with the PR for your improvement.

Create Github workflows to test all (or any relevant modules at least) to build and test S-CORE modules for both x86_64 and aarch64. The workflow should run everyday to identify potential issues as early as possible.

For now, only build the module with `bazel build ...`. I think modules can be "included" under the tests folder, each in its own directory.

Potential initial list of modules:

* baselibs
* baselibs_rust
* logging
* persistency
* lifecycle
* communication

This way we can provide patch files if a module build is broken and then submit these upstream.

Start by inspecting the repository's existing GitHub workflows and the tests folder. Use the listed modules—baselibs, baselibs_rust, logging, persistency, lifecycle, and communication—as the initial scope, and verify the relevant Bazel build targets for x86_64 and aarch64. Done means a daily workflow builds the selected modules for both architectures and exposes failures for follow-up patch files.

Written by the indexing model from the issue text.