standardize regex and messaging for names

[kenafoster]

Reference Issues or PRs

Fixes #1813

What does this implement/fix?

Put a x in the boxes that apply

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds a feature)
• Breaking change (fix or feature that would cause existing features not to work as expected)
• Documentation Update
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Build related changes
• Other (please describe):

Testing

• [X ] Did you test the pull request locally?
• Did you add new tests?

Any other comments?

This splits out the namespace and project name validations into two separate regexes in code since the docs and messaging already imply there are different requirements.

I checked 'breaking change' because this technically DOES restrict project name to 32 characters where it wasn't before. I think anything longer likely won't deploy successfully somewhere down the line because some resources have smaller name requirements, but the documentation and messages previously put a 16 char limit on project names that wasn't actually enforced. But I have no concerns with removing that restriction as well in a follow-up commit if preferable.

Note that I had originally planned to restrict the project name further and/or address other, related bugs around project names (escaping doesn't work in AWS, some other characters such as underscores in project names do not work in practice) but there are other knock-on effects of making these changes so instead I created two new bugs #2001 and #2002 to track.

[iameskild]

Thanks a lot for working on this @kenafoster and @sblair-metrostar!