chore: bump hotdata SDK to >=0.5.0 and rename hotdata-runtime → hotdata-framework references

[eddietejeda]

Changes

Housekeeping for hotdata-ibis:

1. Bump hotdata SDK floor >=0.4.1 → >=0.5.0

• pyproject.toml — dependency specifier
• uv.lock — relocked hotdata 0.4.1 → 0.5.0

2. Rename hotdata-runtime → hotdata-framework references

Terminology-only updates following the rename of the sibling package. No runtime dependency change — the backend still depends on the hotdata SDK; the architecture guardrails continue to enforce that ibis stays independent of the framework package.

• pyproject.toml — description text
• scripts/publish-workflow.sh — usage comment
• tests/test_architecture_guardrails.py — guardrail test names + assertions

3. Drop hotdata-framework from the dependabot allow-list

• .github/dependabot.yml — ibis must not depend on hotdata-framework (enforced by the guardrail tests), so allow-listing it for dependabot was contradictory. Now lists only the hotdata SDK.

Verification

• pytest — 98 passed; ruff check — clean (on hotdata 0.5.0)
• No API drift in the SDK surface the backend imports
• Separately ran the local live integration test (gitignored, not part of this diff) against Hotdata on 0.5.0 — full create/upload/sync + Ibis query/join/aggregate/arrow/drop flow passed end-to-end

[claude]

Clean housekeeping PR. Rename is complete and consistent (no stray hotdata-runtime/hotdata_runtime references remain), and the hotdata>=0.5.0 floor matches the relocked uv.lock.

[claude]

Clean dependency bump and terminology cleanup. Verified: no leftover hotdata-runtime references, dependabot allow-list is consistent with the architecture guardrail (hotdata SDK only), and the uv.lock bump matches the pyproject.toml specifier.