HubSpot data warehouse source: sync engagement associations (meetings/emails ↔ companies/deals) + expose include_history

What I'm trying to do
Read HubSpot CRM data from the PostHog data warehouse instead of calling the HubSpot API directly, to power an account-level engagement view (which accounts we've met/demoed, and how far each deal progressed).

The gap
The HubSpot source materializes CRM↔CRM associations as embedded JSON on companies (contacts, deals, quotes, tickets), but engagement objects are excluded:

• hubspot.meetings and hubspot.emails have no association columns, and companies embeds no meetings/emails JSON.
• So synced meetings/emails can't be joined to companies or deals at all — the association exists in HubSpot but never lands in the warehouse.
• The "Customize synced properties" toggle covers properties only, not associations, so there's no UI path to add them.

Separately, per-property history isn't synced (e.g. a deal's hs_v2_date_entered_<stage> stage-entry dates), so "the furthest/deepest stage a deal ever reached" can't be reconstructed — only the current dealstage is available.

Request
The underlying dlt HubSpot source already supports both — they're just not surfaced. Please expose in the connector:

1. Selectable associations, including engagement objects (meetings/emails/calls/notes ↔ companies/deals/contacts).
2. An include_history option to sync property-change history (e.g. deal stage-entry dates).

Refs: dlt-hub/verified-sources HubSpot settings.py (hardcoded CRM-only association list); PostHog HubSpot source docs; HubSpot Associations v4 / Meetings v3 APIs

The issue points to dlt-hub/verified-sources HubSpot settings.py and the PostHog HubSpot source docs; start by comparing the existing CRM-only association list with the connector settings path. Trace how synced properties are exposed, then verify how selectable engagement associations and include_history should be surfaced. Done means both options are available for the HubSpot warehouse source.