fix(hubspot): use resolveSelectedObjectType in pipelineId/stageId fetchOptions

Both selectors used inline `?? 'contact'` fallbacks while properties and
targetPropertyName already routed through the resolver. Switch to the
shared helper so custom-object handling stays consistent across every
cascading selector.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Author: waleedlatif1

apps/sim/triggers/hubspot/poller.ts

@@ -200,9 +200,7 @@ export const hubspotPollingTrigger: TriggerConfig = {
         const credentialId = useSubBlockStore.getState().getValue(blockId, 'triggerCredentials') as
           | string
           | null
-        const objectType =
-          (useSubBlockStore.getState().getValue(blockId, 'objectType') as string | null) ??
-          'contact'
+        const objectType = resolveSelectedObjectType(blockId) ?? 'contact'
         if (!credentialId) throw new Error('No HubSpot credential selected')
         if (isCredentialSetValue(credentialId)) return []
         try {
@@ -231,9 +229,7 @@ export const hubspotPollingTrigger: TriggerConfig = {
         const credentialId = useSubBlockStore.getState().getValue(blockId, 'triggerCredentials') as
           | string
           | null
-        const objectType =
-          (useSubBlockStore.getState().getValue(blockId, 'objectType') as string | null) ??
-          'contact'
+        const objectType = resolveSelectedObjectType(blockId) ?? 'contact'
         const pipelineId = useSubBlockStore.getState().getValue(blockId, 'pipelineId') as
           | string
           | null