Clang-tidy config for neuland and rolu

[YanzhaoW]

Info:

1. Add separate clang-tidy configuration for NeuLAND and ROLU.
2. The default .clang-tidy located in the project root folder is now a link to config/clang_tidy/global.yml with exactly the same configuration.
3. Configurations for NeuLAND Related folders enable stricter rules (I will personal resolve those warnings for any NeuLAND related PRs).
4. All clang-tidy warnings are disabled for ROLU related detector (as requested from ROLU modified to also run with no trigger and online spectra added #896) because currently no one is available to dedicate on software development of the detector.
5. Add an instruction for the clang-tidy configuration.

Related to #907

---

Checklist:

• Rebased against dev branch
• My name is in the resp. CONTRIBUTORS/AUTHORS file
• Followed the pull request guidlines and the Git workflow
• Followed the seven rules of great commit messages

[YanzhaoW]

Ok, all conflicts resolved. Change the old config to core.yml and apply it to the core utilities in R3BRoot. Put @klenze config to default.yml (which is basically everything disabled).

The core.yml is linked to .clang-tidy files in folder r3bbase and r3bsource/base.

The core configuration is, of course, subjected to any discussion, which should be focused on REASONS of programming and software (as the implementation of core functionalities already requires relative high level of programming).

[jose-luis-rs]

Thanks