DEV-749 Migration to separate shimmer-web-sdk

[Copilot]

The SDK has been extracted to ShimmerResearch/shimmer-web-sdk and published as @shimmerresearch/shimmer-web-sdk. This PR updates the demos repo to consume the published package rather than a local copy, and restores the original root-level GitHub Pages URLs.

Changes

• Demo directories — moved from demos/<name>/ back to repo root, restoring https://shimmerresearch.github.io/webBLEDemos/<name>/ URLs
• SDK imports — all demo index.html files now load the SDK from jsDelivr's GitHub CDN using @latest:

  import { Shimmer3RClient } from 'https://cdn.jsdelivr.net/gh/ShimmerResearch/shimmer-web-sdk@latest/dist/shimmer-ble.esm.js';

  @latest resolves to the newest git tag automatically — no demo changes needed on future SDK releases
• shimmer-ble-sdk/ removed — local SDK source deleted; shimmer-web-sdk is the source of truth
• shimmer-extension/ — import path updated to ../shimmer-web-sdk/dist/shimmer-ble.esm.js; README updated to instruct cloning shimmer-web-sdk as a sibling directory
• Package name — all remaining references to @shimmerresearch/web-ble renamed to @shimmerresearch/shimmer-web-sdk
• README — layout, live demo URLs, and SDK section updated throughout

Prerequisite in shimmer-web-sdk

The jsDelivr GitHub CDN can only serve files that are committed in the tag. The dist/ directory is currently gitignored. Add this step to cut-release.yml after the build step:

- name: Stage dist for release commit
  run: git add -f dist/

Without this, the CDN URL will 404 until the next release is cut with dist committed.

[marknolan]

@JongChern a further step we could take here is to have two repos

1. shimmer-web-ble

• new repo
• contains SDK
• publishable as an NPM to npmjs.com or GitHub Packages

2. webBLEDemos

• existing repo with demo URL paths restored
• references either the NPM (more applicable to end users) or shimmer-web-ble as a submodule.

[marknolan]

@copilot resolve the merge conflicts in this pull request. A note was added to the readme on main regarding the code changes within this PR. I think we can update the note to point any potential users using main to reference the latest release tag if they need to before migrating.

[Copilot]

@copilot resolve the merge conflicts in this pull request. A note was added to the readme on main regarding the code changes within this PR. I think we can update the note to point any potential users...

Done in b4d7ec0. Merged main into this branch — the only conflict was README.md. The migration notice from main has been incorporated as an updated blockquote at the top of our README:

Migration note — this branch replaces the local shimmer3r.js / verisense.js files with the published shimmer-web-sdk package. If you need the pre-migration setup, check out the v0.0.1 release tag.

This points users on main to the v0.0.1 release tag for the last stable pre-migration state before they migrate.