Features/feature name validation

[kyle-ssg]

Thanks for submitting a PR! Please check the boxes below:

• I have run pre-commit to check linting
• I have filled in the "Changes" section below?
• I have filled in the "How did you test this code" section below?

Adding RegEx Validation

feature-name-regex.mov

Only allowing valid RegEx's

[github-actions]

Uffizzi Preview deployment-9188 was deleted.

[matthewelwell]

Using this PR as a place to put this comment but I feel like this is an API issue more than a FE issue.

I tested this using the regex string [a-z]+ and then was able to create a feature called test_feature, whereas I was expecting it to fail. The issue being that I hadn't explicitly stated that I wanted the regex to match the entire string (i.e. ^[a-z]+$).

The question, however, is whether we want to automatically wrap the regex string in ^ and $ to ensure people don't get unusual behaviour like this? Or are we happy giving them full control, but perhaps adding wording that they should wrap their regex in these characters?

Also, I noticed that there is an extra $ being prepended to the regex string in the UI warning on the feature create page which seems a bit misleading.

[matthewelwell]

I think it would be nice, as an improvement to add a 'tester' input next to the input on the project settings page. Not essential but it would be nice.

[kyle-ssg]

I think it would be nice, as an improvement to add a 'tester' input next to the input on the project settings page. Not essential but it would be nice.

Added