feat(createAccount): better error messages/handling on username error

[josephmcg]

What this PR does 📖

• add red border around username while invalid after a user failed submission once
• make error message update along with our Config values (groups and accounts)
• remove unused data

Which issue(s) this PR fixes 🔨
AP-1741

Special notes for reviewers 🗒️
Is the native error better regarding accessibility?

Additional comments 🎤

[netlify]

✅ Yeeeehaw, deploy preview is ready!

Name	Link
🔨 Latest commit	0b4541d
🔍 Latest deploy log	https://app.netlify.com/sites/adoring-edison-dbcef8/deploys/62a142598663b80008e0480d
😎 Deploy Preview	https://deploy-preview-3505--adoring-edison-dbcef8.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[molimauro]

I moved preventDefault lower so the browser error message wouldn't come through. Not sure how we feel about it. Is the native error better regarding accessibility?

Its fine for now :)

[stavares843]

11928301893102.mov

after the error, reloads the page and goes to the /unlock view

[josephmcg]

But thats not a new issue, thats the way it's always behaved. If you want to change that, it should be in a separate ticket

[stavares843]

doesn't happen on dev

Gravacao.do.ecra.2022-06-08.as.14.56.32.mov

actually, i can even say that this bug was almost getting introduced in march on a previous PR

#2447 (review)

as you can see, was fixed as well before merging

[molimauro]

oh its the preventDefault i guess

[josephmcg]

Sara and I discussed. I didn't fully understand the issue. will fix tomorrow

[josephmcg]

@stavares843 should be better now

[stavares843]

thanks @josephmcg 🔨