chore: tag recent mento-sdk releases and cut stable 3.3.0

[chapati23]

Context

frontend-monorepo currently pins @mento-protocol/mento-sdk to 3.3.0-beta.1 because the app borrow flows depend on the beta API.

Live state checked on 2026-07-10:

• npm dist-tags: latest = 3.2.8, beta = 3.3.0-beta.1, rc = 3.0.0-rc.1
• npm versions include 3.2.7, 3.2.8, 3.3.0-beta.0, and 3.3.0-beta.1
• GitHub tags currently stop at v3.2.6 (git ls-remote --tags https://github.com/mento-protocol/mento-sdk.git)

Request

• Push missing git tags for the npm-published versions: v3.2.7, v3.2.8, v3.3.0-beta.0, and v3.3.0-beta.1.
• Publish release notes or changelog entries for those versions.
• Cut and document a stable 3.3.0 release once the borrow API surface is frozen.

Why

The frontend app is using the exact beta pin as a deliberate mitigation, but every money flow depending on an untagged beta package leaves us without normal source provenance, release notes, and a stable promotion path.

Stable 3.3.0 will let frontend-monorepo replace the beta pin in a follow-up PR without changing the SDK integration behavior.