[mountiny]

The publish workflow for #952 stopped halfway. It committed the package-lock.json bump to 2.0.210 (a40e4c2), but the GitHub API returned an empty response for the package.json commit, so the job failed before it tagged and published the release (https://github.com/Expensify/expensify-common/actions/runs/37521663505). A rerun of that job always fails with HTTP 409, because it sends the old package-lock.json SHA from the merge commit.

As a result, main has package.json at 2.0.209 and package-lock.json at 2.0.210, and npm latest is still 2.0.209, so the change from #952 is not on npm yet.

This PR sets package.json to 2.0.210 so both files agree. When it merges, the publish workflow runs from a fresh main, bumps both files to 2.0.211, pushes the tag, and publishes to npm.

Fixed Issues

For Expensify/App#101440

Tests

1. No unit tests cover this change, because it only changes the version field in package.json.
2. Run jq -r .version package.json package-lock.json and verify that both print 2.0.210.

QA

1. After this PR merges, verify that the "Publish package to npmjs" workflow run for the merge commit succeeds.
2. Run npm view expensify-common version and verify that it prints 2.0.211.
3. No regression testing is needed, because no library code changes.

[os-botify]

🚀 Published to npm in 2.0.211 🎉