[v3.4] 494 import equipment

resolves #494 as requested by CSSI; this will need to be merged into `master` as well. I'm going to clean up the branch and remove the testing since it was barely set up; the import was working fine so in the interest of getting the feature implemented I think we should skip testing for now. Additionally, we probably want to refactor all of the import code at some point as well. I'll also verify that all of the changes to the category, equipment model, and equipment object models have been taken into account.
huh. I used a really questionable and slightly confusing naming convention when writing the import users routes two years ago. You adapted the structure to import equipment (import/import_page and imported/import), which is fine so long as we're consistent, but now I'm having second thoughts that what I wrote was really the best.

the ```imported``` route does the actual import*ing*, but it does render the successful-import/"imported" *page* at the end, so, I guess there was a logic.. :P