[23468] Updates after 2.3.1 EOL

[cferreiragonz]

Description

@Mergifyio backport 2.4.x

Contributor Checklist

• Commit messages follow the project guidelines.
• N/A: Tests that thoroughly check the new feature have been added/Regression tests checking the bug and its fix have been added; the added tests pass locally
• Changes are API compatible.
• N/A: Applicable backports have been included in the description.

Reviewer Checklist

• The PR has a milestone assigned.
• The title and description correctly express the PR's purpose.
• Check contributor checklist is correct.
• Check CI results: changes do not issue any warning.
• Check CI results: failing tests are unrelated with the changes.

[rsanchez15]

@Mergifyio backport 2.4.x

[mergify]

backport 2.4.x

✅ Backports have been created

Details

• #283 [23468] Updates after 2.3.1 EOL (backport #282) has been created for branch 2.4.x but encountered conflicts

Cherry-pick of 3a0c756 has failed:

On branch mergify/bp/2.4.x/pr-282
Your branch is up to date with 'origin/2.4.x'.

You are currently cherry-picking commit 3a0c756.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   RELEASE_SUPPORT.md

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	both modified:   .github/pull_request_template.md
	deleted by us:   .github/workflows/nightly-ubuntu-ci.yml
	deleted by us:   .github/workflows/nightly-windows-ci.yml

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally