chore: update version to 0.2.1 due to some publishing issues

[alisonferreira-vnt]

Summary by Sourcery

Bump the project version to 0.2.1 across backend, frontend, and example packages and document that 0.2.0 is invalid due to publishing issues.

Enhancements:

• Mark version 0.2.0 as invalid in the changelog and introduce 0.2.1 with the existing set of changes.

Documentation:

• Update the changelog to reflect version 0.2.1 and clarify the invalid 0.2.0 release.

Chores:

• Update version numbers to 0.2.1 in backend configuration, frontend client, and example app metadata.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Bumps project version from 0.2.0 to 0.2.1 across backend, frontend, and example packages, updates the OpenAPI client config and schema, and amends the changelog to document 0.2.1 and mark 0.2.0 as invalid due to publishing issues.

File-Level Changes

Change	Details	Files
Bump project version from 0.2.0 to 0.2.1 across backend and frontend artifacts.	Update the Python package version in the project metadata Update the frontend TypeScript client package version Update the example frontend package version Update the OpenAPI client VERSION constant to 0.2.1 Regenerate or update the OpenAPI schema JSON to reflect the new version where applicable	pyproject.toml frontend/package.json example/package.json frontend/src/client/core/OpenAPI.ts frontend/openapi_schema.json
Adjust changelog to introduce 0.2.1 and deprecate 0.2.0 due to publishing issues.	Rename the 0.2.0 changelog section to 0.2.1 and update its id anchor Insert a new 0.2.0 section marked as INVALID due to publishing issues	CHANGELOG.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.85%. Comparing base (65a2d3b) to head (6f9da4f).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #215   +/-   ##
=======================================
  Coverage   93.85%   93.85%           
=======================================
  Files          19       19           
  Lines         700      700           
  Branches       51       51           
=======================================
  Hits          657      657           
  Misses         33       33           
  Partials       10       10           

Flag	Coverage Δ
backend-python-3.10	92.67% <ø> (ø)
backend-python-3.11	92.67% <ø> (ø)
backend-python-3.12	92.67% <ø> (ø)
backend-python-3.13	92.67% <ø> (ø)
frontend	100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.