Configure branch names based on specific source branches
<!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.-->
### Proposal
With https://gitlab.com/gitlab-org/gitlab/-/issues/21243, the ability to customize the format of the branch name is possible.
Some groups work using [gitflow](https://docs.gitlab.com/ee/topics/gitlab_flow.html) so having multiple branch formats based on branch types would be useful.
- `feature/`
- `hotfix/`
- `release/`
- `support/`
The ideal solution should support gitflow as well as simpler alternatives such as [Github and GitLab flow](https://docs.gitlab.com/ee/topics/gitlab_flow.html#github-flow-as-a-simpler-alternative).
### User requests for this feature
- https://gitlab.com/gitlab-org/gitlab/-/issues/21243#note_847641635
- https://gitlab.com/gitlab-org/gitlab/-/issues/21243#note_527512062
- https://gitlab.com/gitlab-org/gitlab/-/issues/21243#note_503394338
- https://gitlab.com/gitlab-org/gitlab/-/issues/21243#note_964012837
- https://gitlab.com/gitlab-org/gitlab/-/issues/378297+ (related)
<!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. -->
<!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section.
-->
<!-- Label reminders
Use the following resources to find the appropriate labels:
- https://gitlab.com/gitlab-org/gitlab/-/labels
- https://about.gitlab.com/handbook/product/categories/features/
-->
issue