feat: adapted construct-x connector helm chart configurations

[saudkhan116]

WHAT

Briefly describe what your PR changes, which features it adds/modifies.

• Adapted the controlplane and dataplane templates
• Added seed jobs to inject certificates to the vault
• Updated helm values files; values-consumer.yaml and values-provider.yaml
• The following docker images have been used:
  • Controlplane: registry.onstackit.cloud/constructx/con-x-controlplane-postgresql-hashicorp-vault
  • Dataplane: registry.onstackit.cloud/constructx/con-x-dataplane-postgresql-hashicorp-vault

WHY

Briefly state why the change was necessary.

To demonstrate data exchange using Construct-X connectors and ensure compatibility between IdentityHub, Issuer-service and portal registration service.

FURTHER NOTES

List other areas of code that have changed but are not necessarily linked to the main feature. This could be method signature changes, package declarations, bugs that were encountered and were fixed inline, etc.

Closes # <-- insert Issue number if one exists

[sb-embeteco]

Both deployment options (consumer and provider) worked on my cluster using the deployments from the Construct-X IdentityHub Helm chart PR; see the PR comment in the IdentityHub repository.

Questions:

• Would the deployment using the legacy values file and Tractus-X container still work after the deployment files have been updated to use the Conststruct-X EDC Testbed Container? If not, we might want to consider opening a separate Chart for the Con-X Testbed and restore the Tractus-X Chart.

Notes:

• Since I'm using Istio as the ingress controller on my cluster, I wasn't able to explicitly test the ingress block in the values files. However, I don't think the changes to the configuration will have a negative impact on the deployment.
• The README can no longer be fully applied to the new deployment and should be updated to reflect using the new values files.

done