Task/branch regex

[snehith57624]

Description

Allow users with build and deploy access to change branch name which follows given regex

Fixes #1686

Type of change

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] This change requires a documentation update

How Has This Been Tested?

Tested by changing branch names for a pipeline with given regex which matches and doesn't match regex

Checklist:

• [x] The title of the PR states what changed and the related issues number (used for the release note).
• [x] Does this PR require documentation updates?
• [ ] I've updated documentation as required by this PR.
• [ ] I have performed a self-review of my own code
• [x] I have commented my code, particularly in hard-to-understand areas
• [x] I have tested it for all user roles
• [ ] I have added all the required unit/api test cases