v1.20.0

feat: direct Jira worklog integration in the activity-hours panel (#37)

* feat: direct Jira worklog integration in the activity-hours panel

The panel now connects to Jira itself (read+write API token, encrypted via
safeStorage) instead of handing everything to the assistant:

- shows what's already booked in Jira per day/ticket (badges: not booked /
  partial / booked), including bookings made outside the app
- per-day checkboxes in Log-hours mode so only selected (past) days get booked
- half-logged days book only the remainder: day target minus booked, per ticket
- per-ticket hours are editable; a pinned row re-splits the rest of the day
- "Book Nh to Jira" posts worklogs directly (09:00 local start, activity
  comment, notifyUsers=false) and records them in activity-worklog-log.json
- without a token the old prepare-plan + Claude flow still works

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012ibdMVvaidGVgH4jfh7tkC

* fix: accept Jira API tokens created with scopes

Scoped tokens (read:jira-work/write:jira-work) are rejected on the site URL —
Atlassian only honors them on the api.atlassian.com/ex/jira/<cloudId> gateway.
Connect now tries the site first (classic tokens), then resolves the cloudId
via /_edge/tenant_info and retries on the gateway; the working base is stored
with the credentials and used for all later calls.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012ibdMVvaidGVgH4jfh7tkC

---------

Co-authored-by: Rob Coenen <r.coenen@mendrix.nl>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>