chore: rename sig-project-management to sig-release

[FaGru3n]

Description

• rename repo after disscussion with @giterrific and @SebastianBezold

Pre-review checks

Please ensure to do as many of the following checks as possible, before asking for committer review:

• [x] DEPENDENCIES are up to date. Dash license tool. Committers can open IP issues for restricted libs.
• [x] Copyright and license header are present on all affected files

[github-actions[bot]]

Diff for 3665726c8db8fd1ac408f53ca0b02e74950bb95d:

```diff Printing local diff for configuration at '/home/runner/work/.eclipsefdn/.eclipsefdn/otterdog-configs/otterdog.json' Actions are indicated with the following symbols: + create ! modify ! forced update - delete Organization eclipse-tractusx[id=eclipse-tractusx] there have been 49 validation infos, enable verbose output with '-v' to to display them. ! repository[name="sig-project-management"] { ! name = "sig-project-management" -> "sig-release" } Plan: 0 to add, 1 to change, 0 to delete. ``` ```diff Showing diff to a canonical version of the configuration at '/home/runner/work/.eclipsefdn/.eclipsefdn/otterdog-configs/otterdog.json' Organization eclipse-tractusx[id=eclipse-tractusx] --- original +++ canonical @@ -437,7 +437,6 @@ web_commit_signoff_required: false, }, orgs.newRepo('sig-release') { - aliases: ['sig-project-management'], allow_update_branch: false, secret_scanning_push_protection: "disabled", web_commit_signoff_required: false, ```

[netomi]

I can rename that repo ofc, but is sig-release now the final approved name?

[FaGru3n]

I can rename that repo ofc, but is sig-release now the final approved name?

FYI: @giterrific @Siegfriedk @SebastianBezold

i would say yes!

[netomi]

change applied.