Updated release workflow

[Divyansh-db]

What changes are proposed in this pull request?

Updated the Release workflow.

• Now it creates an actual release instead of draft
• It also automatically pulls the Next changelog info from the tag and uses them in the Release notes.

Deleted some unused workflows:

• release-test.yml - run once in feb, 2025

How is this tested?

N/A

NO_CHANGELOG=true

[Divyansh-db]

@mgyucht Is this workflow still relevant/required?

[github-actions]

If integration tests don't run automatically, an authorized user can run them manually by following the instructions below:

Trigger:
go/deco-tests-run/sdk-py

Inputs:

• PR number: 1060
• Commit SHA: cec8c5de7d0ddfb72f94493f80f1e88ed00c23a5

Checks will be approved automatically on success.

[mgyucht]

This LGTM.

We should keep the TestPyPI workflow if we can. It is useful in case we need to modify the release workflow; otherwise, there is no way to test changes to it. We struggle for this reason with testing the Java release; the only way to test is by actually making a release, and hopefully it is the version you like. (We can kind of work around this by not automatically "deploying" Java releases during tests, but you are still testing in a production environment.)