Luos Engine Release 3.0.0

[nicolas-rabault]

By submiting this PR, you agree with the associated license (MIT) and with our Contributor License Agreement (CLA).

Before to begin

Thank you for contributing to the Luos project!

Before to begin, please follow these steps:

• Ensure that this PR is not a duplicate.
• Add the PR to the Luos contribution project

Feel free to read the Luos contribution's guidelines and the documentation page to have more insight about how to contribute to Luos.

PR Description section

Changelog

Luos Engine 3.0.0

Dependencies:

Pyluos version ≥ 2.3.0

What's new:

🆕 Features:

• #444: Allow synchronized network to bypass differential timestamping management. @nicolas-rabault
• #428: Any kind of Network is now supported, you can make your own. @nicolas-rabault
• #429: Multiple simultaneous network is now supported. You can give multiple networks and Luos will use all of them at the same time to synchronize different services across different networks. @nicolas-rabault
• #435: Add a user dedicated pointer in services allowing to reference specific service structs. @nicolas-rabault
• #435: Luos_engine is now completely independent from Robus. @nicolas-rabault
• #451: Luos_engine filter service sources avoiding intruders or excluded service to reach a target. @nicolas-rabault

🆕 Added:

• #442: Add a Serial network management for every supported target and any native configuration. @nicolas-rabault
• #435: Code coverage measurement on unit tests @nicolas-rabault

🆕 Changed:

• #435: New function naming and configuration, please refer to the documentation luos.io/docs @nicolas-rabault
• #435: Object Dictionary structures now have a raw access allowing to perform computation with value without unit consideration. @nicolas-rabault

🛠️ Fix:

• #229: Fix double detection process occurring at the same time. @nicolas-rabault

Changes

Please choose the relevant options:

• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Related issue(s)

Provide a list of the related issues that will be fixed by this PR.

---

WARNING: Do not edit the checklist below.

---

Developer section

• [Documentation] is up to date with new feature
• [Tests] are passed OK (non regression, new features & bug fixes)
• [Code Quality] please check if:
  • Each function has a header (description, inputs, outputs)
  • Code is commented (particularly in hard to understand areas)
  • There are no new warnings that can be corrected
  • Commits policy is respected (constitancy commits, clear commits comments)

QA section

• [Review] tests for new features have been reviewed
• [Changelog] is up-to-date with expected tags
  🆕 Feature: [Feature] Description...
  🆕 Added: [Feature] Description...
  🆕 Changed: [Feature] Description...
  🛠️ Fix: [Feature] Description...