connects #2190

This pull request updates the calendarization and analysis calculation logic to support passing custom Global Warming Potentials (GWPs) throughout the application. The changes primarily involve updating function signatures and internal calls to accept and propagate an array of custom GWPs, as well as refactoring the usage of the assessmentReportVersion parameter to use a dedicated type. Additionally, there are improvements to the initialization of custom GWPs in the app component.

Support for custom GWPs in calendarization and analysis calculations:

• Updated the getCalanderizedMeterData function and all related calendarization functions (calanderizeMeterData, calanderizeMeterDataBackwards, calanderizeMeterDataFullMonth, calanderizeFullYear, getBillPeriodTotal) to accept and propagate an array of IdbCustomGWP objects, allowing custom GWPs to be used in emissions calculations. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14]

• Updated all calls to getCalanderizedMeterData in analysis and report classes (MonthlyAccountAnalysisClass, BetterPlantsReportClass) to include the new customGWPs parameter, ensuring custom GWPs are available throughout the analysis pipeline. [1] [2] [3]

Refactoring and type improvements:

• Replaced the use of string literals for assessmentReportVersion parameters with the AssessmentReportVersion type throughout the codebase for improved type safety and maintainability. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11]

Custom GWP initialization improvements:

• Enhanced the initializeCustomGWPs method in AppComponent to update and persist any changed custom GWPs before broadcasting them, ensuring the latest values are always used.