PROD-3331: bump example apps to app-sdk 4.68.1 for ExO rename (#11260)

Bump @contentful/app-sdk to ^4.68.1 in examples/experience-toolbar and
examples/experience-auditor. 4.68.1 is the latest published release and
ships the ExO M2 terminology rename: ExperienceNodeType and
ExperienceContext.type are now supersets that accept both legacy
(Fragment/InlineFragment) and canonical (ExperienceFragment/
InlineExperienceFragment, experienceFragment) vocabulary, and
ExperienceSnapshot gains an ExperienceFragment arm.

Both apps consume the rename transitively via the typed sdk.experiences.*
surface (no hardcoded CMA routes or entity-type-string comparisons), so
no source changes were required:
- context.type === 'experience' comparison in experience-toolbar still
  type-checks against the widened union; experienceFragment groups with
  fragment on the secondary badge, which is correct.
- node.nodeType / ExperienceNodeType usages resolve against the widened
  union with no changes.

Verified against 4.68.1: both apps typecheck (tsc --noEmit, exit 0),
build (vite build), and pass their full test suites (toolbar 11/11,
auditor 38/38). No behavioral regression.

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

Author: jshmo

examples/experience-auditor/package.json

@@ -3,7 +3,7 @@
   "version": "0.1.0",
   "private": true,
   "dependencies": {
-    "@contentful/app-sdk": "^4.68.0",
+    "@contentful/app-sdk": "^4.68.1",
     "@contentful/f36-components": "4.81.1",
     "@contentful/f36-icons": "^4.28.0",
     "@contentful/f36-tokens": "4.2.0",

examples/experience-toolbar/package.json

@@ -3,7 +3,7 @@
   "version": "0.1.0",
   "private": true,
   "dependencies": {
-    "@contentful/app-sdk": "^4.68.0",
+    "@contentful/app-sdk": "^4.68.1",
     "@contentful/f36-components": "4.81.1",
     "@contentful/f36-tokens": "4.2.0",
     "@contentful/react-apps-toolkit": "1.2.16",