Sentry: Configure releaser workflow to send release info

[mmmarcos]

Sentry supports automatic releases management via Sentry Release GitHub Action.

We could configure it in our releaser workflow to have releases automatically created on Sentry.

Update: Actually, this is already done in Sentry for parsec3-frontend (see parsec3-frontend releases) via source maps upload. But those releases are not available for the parsec3-libparsec project (see parsec3-libparsec releases)

[FirelightFlagboy]

Given the issue getsentry/action-release#129 is not fixed, I would suggest against using that action since we cannot pin it

Although we could use sentry-cli instead, it allow to manage release for a project.

But since we have multiple job to build our multiple client (and rust lib) we may need to use a "prepare" (and likely a finalizer) job that create the release for sentry for the multiple project.

[FirelightFlagboy]

If we go the CLI route, we likely need to:

• Add a job that perform a sentry-cli release new ...

  https://docs.sentry.io/cli/releases/#creating-releases

• Execute the multiple package jobs that upload debug info + data

  We need a way to indicate those jobs how to reference the newly created release, maybe only using the same version is enough 🤔

• Finilize the sentry release in a finilizer job

  https://docs.sentry.io/cli/releases/#finalizing-releases