Feature/eebus rebased

[mlitre]

Describe your changes

This PR adds a first version of an EEBus module that supports the LPC use case. This module interacts with a go library and uses grpc to communicate with this library.
A test framework was also created to validate this module with the grpc calls.

Changes based on @andistorm 's work in #1127.

Requires:

• Add deps to support eebus in everest-core everest-ci#109
• refactor: Fix warnings and use grpc status and not bool for return grpc-extended-cpp-plugin#1

Issue ticket number and link

Checklist before requesting a review

• I have performed a self-review of my code
• I have made corresponding changes to the documentation
• I read the contribution documentation and made sure that my changes meet its requirements

Related

• newly created repo https://github.com/enbility/eebus-grpc Generic EEBUS binary that provides the grpc service
• newly created repo https://github.com/EVerest/grpc-extended-cpp-plugin Glue Code Generator Extension

Issues to create after merging

• If generation is enabled, check if newly generated files differ from the exisiting ones (check for ci)
• Stabilize Code generator by checking gRPC, protoc and go version in cmake
• Refactor code generator extensions by making it more independent from grpc source code
• Allow configuring of eebus service instead of hardcoded example
  • multiple calls in modules/EEBUS/grpc_calls

[felix-ulonska]

⚠️ PR Affected by Security Incident

This PR was affected by a security incident where a compromised account force-pushed to this branch and closed the PR.

✅ Branch History Restored

We've run an automation that restored the complete history of this branch to the time before the attack. All your commits are preserved. Nothing has been updated in the respective branch in case someone force-pushed after the attack but before our automation.

🔄 Action Required

GitHub won't allow reopening this PR after the close and force-push. Please:

• Open a new PR from your branch to the target branch. You can use the following link to open a new PR: Open PR
• Link back to this PR in the description to include previous discussions

We apologize for the inconvenience.