Translated notifScheduler.js from Angular to React Typescript

commHelper.ts
- Added a temporary "any" return type for getUser because the TS needed it

ProfileSettings.jsx
- Imported the new useSchedulerHelper function (name in progress - need to find a good name for this hook)
- Replaced any instances of the old Angular NotificationScheduler module with the new schedulerHelper hook

notifScheduler.ts
- Translated the file from Angular to React TS
- This file exports a single function which initializes the appConfig and then returns an object containing the functions that the Notification Scheduler functions need (only ProfileSettings.jsx is using this file currently)
- Replaced any instances of moment with Luxon equivalent

Following the Prettier changes in @jiji14 commit bb73676

In order to not mess with commHelper.ts as it is outside of the scope of this issue - related to e-mission#1092 (comment)

During the prettier changes, a bunch of the imports got merged. Undoing in this commit: e-mission@1bfb113

Per e-mission#1092 (comment)

notifScheduler.ts
- Added a User interface that acts as a structure instead of using any for the type

ProfileSettings.tsx
- 2 locations that used moment I replaced with Luxon because the notifScheduler is returning DateTime objects which don't mesh with moment
- Restructured the if(uiConfig?.reminderSchemes) in refreshNotificationSettings to execute the promises at first, and then set the data
- Some Prettier formatting took over here automatically too

…-mission-phone into notifScheduler-rewrite

From e-mission#1092 (comment)

notifScheduler.ts
- Replaced toISO for the date object with toJSDate, per @JGreenlee suggestion: e-mission#1092 (comment)

notifScheduler.ts
- Removed angular (no longer used),
- React useState and useEffect (no hooks used),
- and useAppConfig (pulled in as arguments in the exported functions)

…ed as parameters

ProfileSettings.jsx
- Created scheduledPromise and isScheduling
- Hand these variables as arguments to notifScheduler functions that require it

notifScheduler
- Removed scheduledPromise and isScheduling as they aren't doing anything
- Added isScheduling and scheduledPromise as parameters to functions that require it
- Some prettier formatting came in

…xist" error

notifScheduler.ts
- Added some typing
- Created removeEmptyObjects to remove any empty objects from notifs coming from the cordova plugin

…ed notifs call

notifScheduler.ts
- Added a sort function to the list of notifications before they get scheduled
- I chose to go with id since it's an convenient way to sort, since the id is the number of epoch seconds. the alternative is .trigger.at, but that is a full on JSDate in Luxon which is a string ("Date Thu Nov 16 2023 09:36:17 GMT-0700 (Mountain Standard Time)") and harder to sort

I was not confident that isScheduling would be set properly if it were set as a static variable being passed as an arg, so I used useState and passed the value and set function

We want to standardize on using logDebug, so I replaced all important console.logs with logDebugs that use JSON.stringify for object printouts

notifScheduler.ts
- notifs uses any[], because n.trigger.at is not recognized if we use object[]
- TODO: We may want to create a typing file for these types, such as User, which is currently declared as an interface within this file
- TODO: We will want to add a type for notifs coming from cordova, and for ReminderScheme from the config, but I'm not sure how since ReminderScheme is an object with a variety of inner objects whose keys may or may not be named the same (weekly, week-quarterly, passive, etc.)

cordovaMocks.ts
- Added a reminder mock for the cordova plugin for reminders

notifScheduler.test.ts
- Mock the cordova plugin to return the active reminders
- Test the getScheduledNotifs function

A lot of mocking was required to do this:

globalMocks.ts
- Added log mock for console.alert
- Added log mock for console.error
- Both of these are called in displayErrorMsg, which is why we have to mock them

notifScheduler.ts
- Added a resolve in the if statement for the case of "reminders are already scheduled", so that we don't keep running the test and possibly time-out

notifScheduler.test.ts
- added new mocks for clientStats, logger, commHelper, and notifScheduler
- Added comments for clarity in tests
- Renamed any instances of mockNotifications to mockNotifs for more clarity and to mirror the variable name notifs in the actual file
- Created the new test for updateScheduledNotifs that currently only tests to see if it sees that notifications have already been scheduled and then ends

I also had to adjust the error coming from notifScheduler because it wasn't helping much with the way it was defined before

This tests the final functionality and longest path through this function

…-mission-phone into notifScheduler-rewrite

…-mission-phone into notifScheduler-rewrite

If there are no reminderSchemes in the appConfig, notifScheduler doesn't need to do anything so let's not invoke it.

Also, let's create the type definition for reminderSchemes and use it here in notifScheduler.

notifScheduler.test.ts
- Imported getUser and updateUser so that we can mock them in the tests
- Imported addStatReading so we can mock it to do nothing
- Removed the old way of mocking the implementation of getUser, and the new way allows us to change them per-test
- Added automatic mock for clientStats
- added beforeEach statements to mock getUser inside the describe blocks
-

- Tests to see if setReminderPrefs works when called in the way that ProfileSettings.jsx calls it

… scheduled

- There were many places where I used to/fromMillis instead of to/fromJSDate, causing a type difference that was causing errors
- Added a i18n mock because not having a language code return was messing with the debugScheduledNotifs log outputs
- Added a funcitonality for mockNotifs in the test, so that it can be adjusted, cleared, added to, etc. so that we can test with getScheduledNotifs if it successfully scheduled the notifs