Finish sassc migration

[epugh]

Description

Turns out we weren't done, and we needed to finish eliminating old pure ruby sass in favour of c based sassc which led me through the wilderness of gems. Plus, guess what, we still have coffee script preprocessing which I swear slowed down loading the web app up!

Maybe shaved 10 seconds off the builds? From 2 min 10 seconds to just udner 2 minutes?

Motivation and Context

Quepid is qrashing on Heroku.

How Has This Been Tested?

unit tests and by hand and on circleci.

Screenshots or GIFs (if appropriate):

Types of changes

• [] Bug fix (non-breaking change which fixes an issue)
• Improvement (non-breaking change which improves existing functionality)
• [] New feature (non-breaking change which adds new functionality)
• [] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• [] My change requires a change to the documentation.
• [] I have updated the documentation accordingly.
• [] I have read the CONTRIBUTING document.
• [] I have added tests to cover my changes.
• All new and existing tests passed.