Tracy dependency

[MImran2002]

Issue number: #533

Issue Description: Now that we have an update script that runs frequently, we don't need to check the external tracy database during regular application usage. We should remove the dependency and just use the data that we have locally.
There should be a sanity check, though, to make sure there aren't valid reasons to be checking with Tracy outside of the update script.

Tracy Codes Changed:

• App> login_manager> require_login(): user
• App> logic> adminManagement.py> searchForAdmin(): tracyStudents > databaseStudents; tracySupervisors > databaseSupervisors
• App> controllers> main_routes> laborStatusForm.py> laborStatusForm: students, terms, staffs, departments
• App> controller> main_routes> laborStatusForm.py > userInsert: students, supervisor
• App> controller> main_routes> laborStatusForm.py > getPositions: positions
• App> controller> main_routes> laborStatusForm.py > releaseAndRehire: student, supervisor
• App> logic> allPendingForms.py> overrideOriginalStatusFormOnAdjustmentFormApproval(): position
• App> logic> allPendingForms.py> modal_approval_and_denial_data(): position
• App> logic> allPendingForms.py> checkAdjustment(): newPosition
• App> logic> emailHandler.py> init(): newSupervisor, currentPosition, newPosition
• App> controller> main_routes> search.py> search(): current_students, current_students
• App> controllers> main_routes> laborHistory.py> populateModal(): newPosition, oldPosition
• App> controllers> main_routes> alterLSF.py> alterLSF()
• App> controllers> main_routes> alterLSF.py> fetchPositions
• App> logic> alterLSF.py> modifyLSF()
• App> controller> main_routes> laborStatusForm.py > getPositions
• Moved functions in app> logic> departmentPositions.py> updatePositionRecords() to userInsertFunctions.py

Tracy Codes Not Changed:

• App> controllers> main_routes> alterLSF.py> alterLSF(): oldSupervisors (Because there is a sanity chewck)
• App> login_manager> auth_user(): student, supervisors because of shibboleth
• App> logic> adminManagement.py> getuser(): student, supervisor and usertype because there is a sanity check on whether user exist in the database
• App> logic> allPendingForms.py> overrideOriginalStatusFormOnAdjustmentFormApproval(): tracyuser is kept because there is a sanity check on user in database
• App> logic> allPendingForms.py> checkAdjustment(): newSupervisor because there is a sanity check

TestCase added for (These test are created because getting position have complex peewee in it):

• App> controllers> main_routes> alterLSF.py> alterLSF()
• App> controllers> main_routes> alterLSF.py> fetchPositions:
• App> logic> alterLSF.py> modifyLSF():
• App> controller> main_routes> laborStatusForm.py > getPositions:

Codes changed:
All of the code changed are through replacing Tracy functions and Tracy calls with Peewee calls

UI Testing:

• App> login_manager> require_login(): print the user in the terminal and click log out in the UI to test
• App> logic> adminManagement.py> searchForAdmin(): Go to Sidebar > Administration > manage Administrators > Labor Administrator click the drop down and admins should be populated when you search (The same with SAAS and Fin Aid Admin)
• App> controllers> main_routes> laborStatusForm.py> laborStatusForm:
  Go to the sidebar > New Labor Status Form > Select either Supervisor, Department, Terms and Students (You might need to create a term in administration> manage terms to create LSF form)
• App> controller> main_routes> laborStatusForm.py > userInsert:
  Go to the sidebar > New Labor Status Form > Create a labor Status Form > Add Student > Review > A modal pop up > Click Submit (You might need to create a term in administration> manage terms to create LSF form)
• App> controller> main_routes> laborStatusForm.py > getPositions: Go to the sidebar > New Labor Status Form > Create a labor Status Form > Select Position (WLS) to see if its working (You might need to create a term in administration> manage terms to create LSF form)
• App> logic> emailHandler.py> init(): Trigger any event like creating a new Labor Status Form that will involve an inititation of the emailhandler class
• App> controller> main_routes> search.py> search(): This can be checked through Sidebar > Student Search > Search any student
• App> controllers> main_routes> laborHistory.py> populateModal(): Side Bar > Labor Status Form > Create labor status form that is aimed to create the same position for the same term to recreate an error that involves both old position and new position

[BrianRamsay]

We don't need to get the user object again, because it is initialized by the call to auth_user

[BrianRamsay]

Since we don't check other entries before creating, our test will fail if duplicate data exists (which is ok). Since it's already going to fail, we don't need to get_or_none and check for supervisor existence.

[BrianRamsay]

getting the active positions should happen from Tracy, not LaborStatusForms. We should also name this script with a verb, like updateActivePositions. WE probably also want to do the department update in this script, since they are pulling from the same table and dept should be updated before active positions