Adding release action

[dwertent]

Overview

This PR introduces a new GitHub Action workflow called release, which can be triggered either by creating a tag or manually.

The release action orchestrates the following release steps:

1. Release Images – Builds and releases Docker images.
2. Release Charts – Packages and releases Helm charts.
3. Release TypeScript SDK – Publishes the TypeScript SDK.

Each release step is modular and can also be executed independently as a manual action.

[awrichar]

Does this mean the releases are always tied together? I can see us potentially iterating rapidly on the TypeScript SDK to add additional methods (it's pretty incomplete right now). But each time we implement a method, we'll be bumping the version and releasing everything in Paladin?

[dwertent]

No, the TypeScript release can be executed separately.

The dependency between the chart release and SDK release is in place for scenarios where updates have been made in the SDK that aren’t yet reflected in the chart. In these cases, it’s best to release the chart first, followed by the SDK, to ensure compatibility.

However, if you’re still developing the SDK and the required functionality is already available in the chart, you can manually release the SDK.

[awrichar]

Perfect. I think we'll get to a point that it makes sense to release everything together. For now, I think the SDK will be playing catch-up to expose everything that Paladin already does... and I want to avoid doing releases of the operator if nothing in Paladin has actually changed, as it could be confusing to have a bunch of releases that don't actually have any new functionality.

[awrichar]

We should make sure the name in package.json matches the LF Decentralized Trust org. I think it should be @lfdecentralizedtrust-labs/paladin-sdk based on Discord conversation.