Instead of using Tabulator to perform the AJAX request that gets the
data to populate tableData, perform the AJAX request separately and
update the table. This will make it easier to perform separate AJAX
requests as each term (Q1, Q2, Q3, Q4) is requested.

1) The schedule-scraping has been commented out of scrape_student in
scrape.js, instead exporting scrape_schedule directly.
2) A new endpoint, '/schedule', has been declared in serve.js, from which
the schedule can be retrieved as JSON (because it is no longer included
in the JSON file from /data).
3) The JavaScript in home.html now performs the schedule request separately
with a separate callback function, and clock.js no longer assumes
that tableData.schedule must exist if tableData exists.

A similar treatment will be given to other components that are scraped
until the loading has become sufficiently modular (lazy loading)
to make it feasible to retrieve data from past terms and to extend
Aspine in other ways in the future.

Same as previous commit, but with the PDF files (Reports tab).

…iting it. This fixes the problem where tableData already contains information, for example pdf_files, which are then erased when /data does 'tableData = response'. This would occur when a user immediately navigates to the 'Reports' page before /data has the chance to complete.

…hat /data returns while the user is on a different tab