Onboarding workflow

We may need to introduce changes to the onBoarding code to support the GUI teams. The following guidelines outline the process for making and delivering these changes.

1. All development work should be performed in the torus/sztpd.git branch.

2. The Torus team follows a workflow consistent with ours, including the use of Gerrit for patch submission.

3. All backend-related changes must include Torus developers as reviewers to ensure alignment with their standards and expectations.

4. Appropriate test coverage is required for all submissions. Both unit tests and API tests are available in the repository and can be used as reference - examples.

5. An auto-verifier is in place and will automatically execute the unit test suite for each patch set, similar to our internal process.

6. After code is pushed, the system triggers serenity tests as part of the daily build pipeline.

7. To execute these serenity tests locally, use the command 'make test-serenity'.

8. It is strongly recommended to run the serenity tests locally before submitting any code.