UX bug - regex not matching a correct peer address

[koxon]

Describe the bug
If the peer address contains /quick-v1/ instead of /quick/ the field can't be validated and remains in error

To Reproduce
Steps to reproduce the behavior:

1. Go to 'PEERS'
2. Click on 'Add connection'
3. Try to add an address that contains /quick-v1/. Here is one: /ip4/54.90.162.249/udp/4001/quic-v1/p2p/12D3KooWS2xWyVAQA1Hr52mM52hxpBvV5fvrWPeZF1Ck8jes6LrH
4. See error

Expected behavior
latest version of ipfs creates those address so they should be supported

Screenshots

Desktop (please complete the following information):

• OS: Mac Os
• Browser chrome
• Version 0.32

[welcome]

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment.
Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

• "Priority" labels will show how urgent this is for the team.
• "Status" labels will show if this is ready to be worked on, blocked, or in progress.
• "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.io if you just need general support.