Add Landing pages views for Hubspot#1839

The current HubSpot connector does not expose page-level view metrics for Landing Pages. Existing analytics fields (analytics_rawviews, analytics_standardviews, analytics_visits, etc.) are aggregated at the account/site level only, with breakdowns limited to sessions, sources, geolocation, utm-campaigns, utm-contents, utm-mediums, utm-sources, utm-terms. There is no dimension to break these down by individual landing page. formanalytics_formviews only covers form views, not full page views. The blogpost object is fully modeled (URL, slug, state, etc.) but has no matching landingpage object at all, and none of the objects carry a views metric per page.
What HubSpot’s API supports (confirmed via official docs/community):

Endpoint: GET https://api.hubapi.com/analytics/v2/reports/landing-pages/total?start=YYYYMMDD&end=YYYYMMDD
Returns landing page details per portal, with page views as one of the response fields, keyed by page ID.
To resolve page ID → page name/URL, this must be cross-referenced with the COS Page Publishing API (“Get a Page by ID”).
Legacy Analytics Views reference: https://legacydocs.hubspot.com/docs/methods/analytics-views/get-views
Native UI equivalent (confirms the same underlying data exists): “Website page performance” report under Content > Landing Pages > Analyze tab. https://knowledge.hubspot.com/website-and-landing-pages/analyze-performance-for-all-pages

Requested implementation:
Add a new landingpage object to the HubSpot connector (parallel structure to the existing blogpost object), with fields such as:

landingpage_id
landingpage_name
landingpage_url
landingpage_slug
landingpage_state (published/draft)
landingpage_views (numeric — pulled from the landing-pages/total analytics endpoint)
landingpage_created / landingpage_updated

This would let users pull page-level view counts and join them to page metadata, similar to how blogpost_* fields work today, closing the gap between what HubSpot’s native reports show and what’s available via Windsor.