feat(ci): add generic rust ci workflow and include controller/scheduler call

[charley04310]

What is this PR for ?

This pull request introduces 3 new GitHub Actions workflows to improve the continuous integration (CI) process for all the teams working on the codebase :

1. controller.yaml and scheduler.yaml:

They are both sharing the same template to streamline their CI processes.

• Trigger event: These workflows are triggered on every push event that modifies any files in their respective directories.
• Purpose: It serves as a specialized CI workflow for changes in the respective teams directories, ensuring that all updates to these components are tested.

2. rust-ci.yaml:

• Trigger event: This workflow can be invoked manually from any directory using a workflow call with an entry specifying the target directory.
• Purpose: It provides a generic CI workflow for Rust codebase, allowing teams to test various components with a simple input setup. This workflow focuses specifically on ensuring code formatting and linting compliance.

Tests

You can find all passed test here

[sameo]

Where do we actually build the code?

[charley04310]

I'm not sure to understand ? Do I also need to add a build test ?

[sameo]

Yes. A CI should at least build the project and all its components.