Fix user data form bug

[annavik]

The save button was not triggering form submit when editing user info. The problem was the submit button was actually rendered outside the HTML form tag (not sure when this happened?). In this PR we fix this!

The problematic button:

[netlify]

✅ Deploy Preview for ami-dev ready!

Name	Link
🔨 Latest commit	ca65807
🔍 Latest deploy log	https://app.netlify.com/sites/ami-dev/deploys/674dd7c12e144800081d9e73
😎 Deploy Preview	https://deploy-preview-642--ami-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 73 Accessibility: 89 Best Practices: 92 SEO: 100 PWA: 80 View the detailed breakdown and full score reports

---

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

[mihow]

I noticed this but thought is was a fluke. Thanks for fixing! What kind of test do you think can catch this type of issue / regression?

[annavik]

I would probably suggest manual regression testing here as a first step (define a regression test plan and make updating user info part of this). When regression testning is part of our release process, I think a good next step could be to look into tools for automation. Cypress, Selenium and Pupeteer are examples of some tools that can be used to simulate browser interactions.

What are your thoughts?

[annavik]

I will merge this now, but let's talk more about regression tests if you think it's a good idea! :) I think it could make sense to have this part of our process once we start to do a bit more controlled releases?