feat: restore the cluster deployment layer under clusters/sandbox

[jpmewenemesse]

Description

• Restore the OKDP cluster deployment layer under clusters/sandbox/
• Contexts are restored with the improved naming introduced in platform-packages
• Reference packages at the new unversioned OCI path
• Fixed bug related to triggers list (synchronize instead of synchronized)
• Brought back deployment validation workflow from platform-packages without the packages build and publish related stuffs
• Brought back ci deployment validation workflow from platform-packages without packages build and publish related stuffs

Related Issue

Fixes #64

Type of Change

• Bug fix
• New feature
• Documentation update
• Refactor / chore
• Breaking change

How to Test

• Do a complete okdp sandbox deployment under the new files and folder structure
• No deployment failed by issuing kubectl get po -A or kubectl get release -A should show READY for all of the releases

Checklist

• I have tested my changes
• Documentation updated if needed
• If breaking change: migration path described above
• I hereby declare this contribution to be licensed under the Apache License Version 2.0.
• I hereby agree to grant TOSIT a copyright license to use my contributions.

[idirze]

Hello,

Approving functionally.
Note: The commit history does not include the original commits (authors).

[jpmewenemesse]

Hello,

Approving functionally. Note: The commit history does not include the original commits (authors).

I did not moved the commits from other work. I just copied the files themselves as the file structure is different

[mdrutel]

I tested on a fresh cluster :

• Installation of a cluster
• Test of service installation
  Everything is OK

Functionally OK. Provenance can be discussed with other reviewers.

[alex-mabrouk]

I think we can make this endpoint backend-neutral as well.

Since the sandbox currently exposes a single default object storage, consumers don't need to know whether it's backed by SeaweedFS, RustFS or another S3-compatible implementation.

Using a stable hostname such as s3. (and s3-console.) keeps the public endpoint aligned with the storage contract and avoids leaking the backend implementation into the sandbox configuration.

This also makes future backend switches transparent without changing the external URLs.

Suggested change

	endpoints:
	apiUrl: https://seaweedfs-{{ .Release.namespace }}.{{ .Context.ingress.suffix }}
	stsUrl: https://seaweedfs-{{ .Release.namespace }}.{{ .Context.ingress.suffix }}
	consoleUrl: https://seaweedfs-console-{{ .Release.namespace }}.{{ .Context.ingress.suffix }}
	endpoints:
	apiUrl: https://s3.{{ .Context.ingress.suffix }}
	stsUrl: https://s3.{{ .Context.ingress.suffix }}
	consoleUrl: https://s3-console.{{ .Context.ingress.suffix }}

[rpignolet]

Please open a new PR for this subject.