Handle multiple backends for the TypeInstance upload from workflow

[mszostok]

Description

Blocked by: #630

Modify TypeInstance create/update actions (named as "Argo actions") to take new input context as described in 3rd,4th and 5th step: Workflow syntax - Create

For backward compatibility:

• Modify Helm and Terraform runners output and additional output under nested value property in Argo artifact
• Make sure all manifests are up-to-date (at least compatible with new Argo artifact syntax)

Acceptance Criteria

• "Argo actions" reads mounted artifacts and render a proper GraphQL createTypeInstances mutation. Setting relations with a given backend should be skipped as it's done on Local Hub side.
• Handle context propagation in the Local Hub. Send in to a given backend if available.
• Create dedicated Capact manifests or update existing ones to showcase usage of the backend.context in Implementation manifest.
• Update integration test to test the backend.context propagation. We can use the dotenv provider, see: Configure Secret storage backend to be used with Local Hub #647

Related issues

See epic #604 for reason and use cases.

[mszostok]

Extracted setting backend ID (making it mutable) to dedicated issue: #636