Separate user friendly test zols (for SAAS) and actions tests zols

[lydiagarms]

Overview

In the Starlight SAAS for the free subscription plan the customer will only be able to deploy a fixed set of test contracts. We need to pick some user friendly contracts from our current test contracts. There is an old draft PR in starlight that separates user friendly test contracts and action tests (no longer compatible due to test contracts changing significantly). We also want to ensure that these user friendly test contracts are as stable as possible. Therefore, we should finish another draft PR that includes linting for orchestration files.

Tasks

Choose the user friendly test contracts for SAAS with input from Wenxing.
As in the draft PR, separate the user friendly and action test contracts in starlight.
In the testing draft PR, fix unsupported package error message.
In the testing draft PR, remove any unnecessary errors, i.e. formatting, and fix any real errors so that the tests pass.

Optional

If necessary create new user friendly test contracts.

Definition of done

The user friendly and action test contracts should be separated into different folders. The user friendly contracts should be provided to Wenxing.
The linting of orchestatration files should be incorporated into the testing.

Links

The draft PR separating user friendly and action test contracts:
#164

This draft PR includes linting.
#340