*smarter* Take advantage of cached schedule data

Just like the rewritten manage-ftd page, this page no longer performs
the needless calls back to sharepoint for instructor schedules.  Since
splitting the schedule page to an FTD-only page, we’ve always had the
cached data anyway, now we are taking more advantage of that data to
simplify the program and speed things up even more.
Temporary selectize fix

This one probably needs a second look.  Is there any use-case for not
having data.Id?  I think we’re safe now after removing AFSC/MDS, but
worth keeping an eye one.  This was to fix some funky bugs with
selective lists bound to other lists with existing data.  Though it
sounds odd is actually a very common scenario in FTSS.
Updated request to also use cached schedule
Fixed bug after seat request

This was a naming conflict that only showed up after requesting a seat.
Seat Request tweaks

Added message informing users that Schedulers and FTD seat requests
would be auto-approved.