Handle new course faculty type notifications and user settings.

[jullia02]

Summary of Changes

This PR solves issue #6
This PR adds code to successfully add a new notification type of course faculty reply. This is done by adding support to handle a new notification type to
install/data/defaults.json,
src/notifications.js,
src/upgrades/1.7.6/notification_types.js,
src/topics/create.js,
public/openapi/components/schemas/SettingsObj.yaml
and notifications.json of multiple languages (English UK, English US, French, Español, and Arabic).

It also adds an upgrade script that is designed to add this new notification setting for all users in the system. (src/upgrades/3.8.4/add_faculty_reply_notification_setting.js). To reflect these changes in the notification settings, I added code to src/user/settings.js. This added code handles user preference for this new notification feature. Lastly, I added basic test cases to test this new features functionality to test/notifications.js.

All these changes meet the acceptance criteria of having "An option to select notification preferences for course faculty replies appears on the settings page. Choosing an option successfully updates user notification preferences."

Reflection of Changes

• Unique tag of [COURSE FACULTY] and separation from normal user replies.
  
  
• Separate toggle for notification preferences for faculty replies in user settings.

Notes and Progress on Milestone

Underestimated time and effort required: I initially estimated this task to be around 6 hours as I thought I have completed the implementation of the notification on sprint 1 and only needed to work on making the button on the user settings page work. However, after learning more on how the user settings page works, I realize that the notification system from sprint 1 was not fully functional and required significant rework. It required modifications to the database schema and user preferences handling. As well as I realize I needed an upgrade script to add the new setting for all existing users which was an unexpected task. I also spent some time testing this feature and creating test cases to cover its functionality which is added in test/notifications.js

[coveralls]

Pull Request Test Coverage Report for Build 11264670343

Details

• 14 of 15 (93.33%) changed or added relevant lines in 3 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.004%) to 82.711%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
src/user/settings.js	2	3	66.67%

Totals
Change from base Build 11025903872:	0.004%
Covered Lines:	22348
Relevant Lines:	25602

---

💛 - Coveralls

[mhli1260]

Your code looks good to me! Your commits were explanatory of the code you were updating, and your code looks well organized and formatted.