connects #2233

This pull request focuses on improving date handling throughout the analysis and data migration logic. The main changes include standardizing how dates are processed (favoring local time over UTC), updating data migration routines to add explicit month, year, and day fields, and utilizing helper functions for date comparison and predictor data selection. These changes enhance consistency and reliability in date-related calculations and data migrations.

Date Handling Standardization:

• Replaced usage of getUTCFullYear() and getUTCMonth() with getFullYear() and getMonth() across multiple analysis classes to ensure local time is used for year and month calculations. This affects classes such as AnnualAnalysisSummaryDataClass, MonthlyAccountAnalysisClass, MonthlyAnalysisSummaryClass, and others. [1] [2] [3] [4] [5] [6] [7]

• Updated filtering and data grouping logic to use helper functions like checkSameMonth for consistent month comparisons, replacing direct property checks. [1] [2] [3] [4] [5]

Data Migration and Enrichment:

• Enhanced data migration routines to populate and persist month, year, and day fields in predictorData and meterData records if not already set, marking them as migrated. This ensures that all records have explicit date components for future processing. [1] [2]

• Modified the signature of setPredictorDataV2 to accept an additional boolean parameter, likely to control migration behavior.

Predictor Data Handling Improvements:

• Changed the way the latest predictor data is determined by using the new getLatestPredictorData helper instead of _.maxBy, and ensured that date extraction uses getDateFromPredictorData for consistency. [1] [2]

• Updated filtering of predictor data for a given month to use the explicit year and month fields, improving reliability over date string parsing. [1] [2]

Imports and Dependency Updates:

• Added imports for new helper functions (checkSameMonth, getDateFromPredictorData, getLatestPredictorData) in relevant analysis classes to support the above logic. [1] [2] [3] [4] [5]

These changes collectively improve the robustness and consistency of date-related logic throughout the application.