[MIN-321] form for reporting errors in minerva

[Link to bug report |https://appunite.slack.com/archives/C068W173NFJ/p1712306018168669]

Description

Environment

Console logs

Source URL [https://minerva-frontend-parkinson.vercel.app/?id=bubbels&perfectMatch=false&modelId=52&backgroundId=13&x=13389.625&y=6751.5&z=4|https://minerva-frontend-parkinson.vercel.app/?id=bubbels&perfectMatch=false&modelId=52&backgroundId=13&x=13389.625&y=6751.5&z=4] Steps to reproduce open page (in fact this page opens valid project and if the issue with accessing projects without permission is resolved the error there will disappear) Expected result vs actual result In the minerva we have a feature that allows user to report information about errors when frontend/backend throws an exception. Currently it's not implemented in the new frontned (which makes a lot of sense since at the beginning you would produce a lot of noise), but I think it's time to add it. It should work as follows: a) If at any time backend returns 500 or any other status that is unexpected provide user with form that allows him to send information. b) If frontend has some issue (for example Zod validation throws an exception) provide user with form that allows him to send information.I just noticed that I never documented endpoint for that. It's a flat json post with following fields (all strings) /minerva/api/minervanet/submitError:   url - url where it happened   login - user login   email - user email   browser - browser;   timestamp - when it happened;   stacktrace - js stacktrace with error message (if the problem is on backend we should also provide stacktrace how we got there)   javaStacktrace - java stacktrace (only for 500 error on backend);   comment - user comment All fields except stacktrace and javaStacktrace should be optional (user can decide to not send such information)I remember that Mateusz Supel has prepared visualization for that

---

Issue metadata

• Issue type: Bug
• Priority: Medium