add render context prop to sentry error event

[anton202]

Fixes

Fixes #1620 by @sarayourfriend

Description

added render context property to the sentry event that is sent when there is an error
screenshot
i`ve tested it on my own sentry account and it seems to work...

Testing Instructions

someone with access to sentry needs to test this.

1. go to util/sentry-config.ts
2. paste the project dsn in the dsn property.
3. comment out the disabled and clientConfig property.
4. go to pages/index.vue
5. insdie setup(), throw an error
6. open the project in the browser.
7. go to sentry, look for that error and check if there is render context -> platform: server, in the report.
8. got to pages/index.vue again. now, encapsulate your error with an if statment that checks if the proccess is client
   if (process.client) { throw new Error('test index page') }
9. repeat step 6 and 7, but now the platform should be client.

Checklist

• My pull request has a descriptive title (not a vague title like Update index.md).
• My pull request targets the default branch of the repository (main) or a parent feature branch.
• My commit messages follow best practices.
• My code follows the established code style of the repository.
• I added or updated tests for the changes I made (if applicable).
• I added or updated documentation (if applicable).
• I tried running the project locally and verified that there are no visible errors.

Developer Certificate of Origin

Developer Certificate of Origin

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

[zackkrida]

I like this approach and it appears to work for me, too. Thanks @anton202!

[sarayourfriend]

Brilliant, thank you 🚀

[sarayourfriend]

I've created #1963 to account for the flaky e2e test needing to be addressed.