Normalize `release` option

### Description

Currently we read out the `versionName` as-is, but the customer can set any random string in there, which will break our release health feature (and everything around releases in general). So we should try to normalize the `versionName` to comply with SemVer (e.g. relax the semver regex by excluding a prepending `v` for example, if the version was set to `v1.2.3`).

If the version is still not a valid semver after normalization, we should fail/print a warning and let the customer know that the release feature won't be working correctly in some cases.

Related to:
* https://github.com/getsentry/sentry/issues/76502

先找出讀取 release 選項或 versionName 的位置，以及目前進行 SemVer 驗證的位置。檢查 SDK 如何發出警告，然後確認常見的帶前綴版本會被正規化，並確認仍然無效的值會產生清楚的警告，說明 release 功能將無法正常運作。

由索引模型根據 Issue 內容生成。