feat: trigger Jira issue automation on PR merge event

[andrey-canon]

This PR improves the GitHub Actions workflow responsible for creating Jira issues by:

• Dynamically generating the story and sub-task information based on repository and pull request metadata.
• Automatically assigning the appropriate deployment environment based on the target branch.

These changes enhance automation and reduce manual effort when tracking development work in Jira.

[johanseto]

Rebase this PR or review it before to run tests.

#3

[andrey-canon]

Rebase this PR or review it before to run tests.

#3

Is the pr #3 already included in the teak version ?

[johanseto]

Rebase this PR or review it before to run tests.
#3

Is the pr #3 already included in the teak version ?

The rebase is manually, so it has only commits for tests. The other thing is to make open-release/redwood.master starts from the version of teak..

[andrey-canon]

The rebase is manually, so it has only commits for tests. The other thing is to make open-release/redwood.master starts from the version of teak..

You didn't answer my question, those commits that you included in the pr #3 were already included in the sga version which is compatible with teak ? I just want to know if we will have to migrate that

[johanseto]

The rebase is manually, so it has only commits for tests. The other thing is to make open-release/redwood.master starts from the version of teak..

You didn't answer my question, those commits that you included in the pr #3 were already included in the sga version which is compatible with teak ? I just want to know if we will have to migrate that

Seem that yes until v0.25.3
https://github.com/openedx/edx-platform/blob/release/teak/requirements/edx/base.txt#L514
https://github.com/mitodl/edx-sga/commits/v0.25.3/
maybe in the official release they could use 0.26.0 that comes with django 5.1 support

[johanseto]

I would merge fix actions, after this PR. To keep it tracked =)