chore(iobroker.teslemetry): enable npm publish

[Bre77]

Intent

• iobroker.teslemetry still had private: true, so the changesets publish pipeline (pnpm run ci:publish in .github/workflows/publish.yml) skips it even though the two prior repochecker blockers (io-package.json version/news sync, admin icon) are already merged (fix(iobroker.teslemetry): sync io-package.json version/news and add admin icon #53).
  • Fix: dropped private: true from packages/iobroker.teslemetry/package.json.
• io-package.json had drifted again - the 0.1.10 dependency-bump release (@teslemetry/[email protected]) went out via the version-packages pipeline, which only touches package.json/CHANGELOG.md, so io-package.json's common.version was back to 0.1.9 with no 0.1.10 news entry.
  • Fix: synced common.version to 0.1.10 and added the matching news entry.
• Added a changeset (.changeset/iobroker-first-publish.md) so the next Version Packages PR picks up this package and mints its first real npm release.

Testing

• pnpm --filter iobroker.teslemetry build - clean
• pnpm --filter iobroker.teslemetry check - clean
• pnpm --filter iobroker.teslemetry test - 30/30 pass
• pnpm lint - clean

This PR does not publish anything itself - merging it lets changesets open a "Version Packages" PR for iobroker.teslemetry; publishing to npm happens only when that follow-up PR is merged, via the existing OIDC/provenance publish step.

Next steps (outward, after npm publish)

Publishing to npm is half of going live - the adapter also needs listing in the ioBroker adapter store, which is a separate manual submission against ioBroker/ioBroker.repositories:

1. Once iobroker.teslemetry exists on npm, open a PR there adding an entry to sources-dist.json pointing at this package (npm and/or GitHub source).
2. Their CI runs @iobroker/repochecker against the submission - it needs the npm package to already be published to fetch and check the tarball, checks io-package.json metadata (version/news sync, icon, license, type, all fields this PR and fix(iobroker.teslemetry): sync io-package.json version/news and add admin icon #53 already keep in sync), README structure, and repo conventions (LICENSE file, changelog format).
3. After repochecker passes, an ioBroker maintainer manually reviews the adapter before merging - this is community-run and typically takes 1-2 weeks, not something we control the timeline on.
4. Once merged there, the adapter becomes installable from the ioBroker admin UI's adapter list (still "latest"/unstable until a further stable-repo promotion, which follows ioBroker's own install-count/stability criteria).