[BUG] Strava MCP Connector —  getLoggedInAthleteActivities  returns empty array for 2026 date range

**Describe the bug**
The activity list tools consistently return an empty array when querying activities from 2026, despite the athlete having confirmed activity data for that year.

Environment:
• Platform: Pipedream MCP (Strava integration)
• Tools affected:  strava-get-activity-list ,  strava-search-activities 

**To Reproduce**

1. Call  **strava-get-activity-list**  or  **strava-search-activities**  with the following parameters:
- after :  1735689600  (Unix timestamp for January 1, 2026, 00:00:00 UTC)
- before :  1749650000  (Unix timestamp for June 11, 2026)
- maxItems : 100

2. Observe that the response returns an empty array:  "ret": [] 

**Expected behavior**
The tools should return the athlete’s activity list for 2026. The athlete has confirmed they have training data for this period visible in the Strava app.

**Screenshots**

**Additional context**

- The  strava-get-athlete-stats  tool works correctly and returns accurate 2026 year-to-date data.
- When querying activity data for 2025 (e.g.,  after: 1735603200 ), the tools return results as expected.
- The problem seems to be related to how the connector handles Unix timestamp filtering for dates in 2026, possibly a parameter passing or epoch calculation issue on the connector side.

Impact:
This issue makes it impossible to retrieve, analyze, or process any individual activity data for the current year (2026), significantly limiting the usefulness of the Strava MCP integration.