Extract non-class meetings and course instance tables into a generic component

[rmainwork]

As things currently stand, the course instance table

and the Non-class meetings table

are essentially the same thing,. but are implemented as separate components.

Ideally, they should be refactored into one generic re-usable component (similar to the current implementation of the course instance table) that can show the columns passed as props. This would allow us to have tests for only one implementation of the complex table layout, and keep the logic for it in one place(as well as only having to test it once).

Perhaps an array of columns could be provided, with offset numbers for the start and end of the fall/spring header columns to determine which columns they sit above on the table.

<SemesterTable
  columns={/* some array of column data goes here (maybe reformatted table data?) */}
  fallColumnStart={/* the first column number that should be considered part of "Fall <academic year> -1 "*/}
  fallColumnEnd={/* the last column number that should be considered part of "Fall <academic year> -1 "*/}

  springColumnStart={/* the first column number that should be considered part of "Spring <academic year>"*/}
  springColumnEnd={/* the last column number that should be considered part of "Spring <academic year>"*/}

  // ... Other props
/>