Pushing dept/school data to DB

[MasterFardeen15]

Description & Fixes # (issue)

Pushing department data to DB:
In db_init.py, added an argument for addDept to add schools/dept from json endpoint to database. Updated functions and addDept code. Follow same coding style as used in addCourses.
Department/school data can now be pushed to the Database. Dept data is only added to the DB, if not found in the DB.

• [x ] Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

In powershell:
For testing addDept:
python db_init.py addDept https://raw.githubusercontent.com/quacs/quacs-data/master/semester_data/202409/schools.json

For testing addCourses:
python db_init.py addCourses https://raw.githubusercontent.com/quacs/quacs-data/master/semester_data/202409/catalog.json

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works (if a larger change)
• New and existing unit tests pass locally with my changes

[deepsource-io]

Here's the code health analysis summary for commits 3c22324..7cb0300. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
Python	❌ Failure	❗ 2 occurences introduced 🎯 1 occurence resolved	View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[RafaelCenzano]

LGTM