Nav updates for #34, and bring code changes from staging into this repo

[benlk]

Changes

This pull request makes the following changes:

• Updates Grunt so that Grunt can compile in newer versions of Node
• Removes style.min.css because it looks like someone was editing that by hand on staging, which is a fate I wish on no person
• Removes references to the homepage CSS, which was removed in acd44a2
• Copies updates from the staging/prod env:
  • different INN logo
  • new Typekit kit
  • nav color change to #f3f4f3, which I'm calling @beige
  • reduce footer font size to 14px
• update fonts in LESS to match changed Typekit
• zeroes out Largo's header, for Update navigation on new sitebuilder homepage #34
• style changes as described in Update navigation on new sitebuilder homepage #34 (comment)
• bumps Largo to release 0.6.4 to match staging 😨
• resolves Remove files triggering Dependabot PRs #38 by removing the affected files

Why

For #34

Also because there were code changes made on prod/staging that were not reflected here.

Testing/Questions

Features that this PR affects:

• Header on all pages
• The main and secondary navs as inserted into a SiteOrigin page builder

Questions that need to be answered before merging:

• Is this PR targeting the correct branch in this repository?
• Is something wrong with the sticky nav?

Steps to test this PR:

1. In Settings > Reading, set the homepage to the "NEW HOMEPAGE TESTING" page
2. Edit the "NEW HOMEPAGE TESTING" page in the SiteOrigin page builder. In the Topper section, in the second Layout Builder element, edit that Layout Builder:
   • remove the text widgets containing the mocked-up html menus
   • add an Enhanced Text widget with the following content:

<?php
    get_template_part( 'partials/nav', 'main' );
    get_template_part( 'partials/nav', 'secondary' );
?>

3. view the homepage.

[benlk]

This is now ready for review.

[benlk]

Notes from review:

• figure out why the sticky nav is showing up
• blank space is caused by this markup, which must be hidden via CSS:
  
• the different layout at different screen sizes is in fact a different layout within the Pagebuilder, which will also need to be updated, or if we can get the Pagebuilder to hide the entire layout below a certain screen size — but I think Sonya should make those changes on the staging site, and copy them to prod
  
• How will we copy these changes from Staging to Prod? Needs a bit of research; deploying this PR for review will provide a good time to do that testing.

[benlk]

In the SiteOrigin page builder:

• For the Enhanced Text widget, disable automatic addition of paragraphs
• For the row containing the Enhanced Text widget, click the wrench icon, then under Layout set "Cell Vertical Alignment" to "Top"

That plus the CSS in a7e3b5e get us to this:

[benlk]

Regarding exports: https://siteorigin.com/page-builder/exporting-content/

SiteOrigin PageBuilder does not appear to have a way to export a single post. Our options for transferring from staging to prod are:

1. Recreate changes by hand
2. Transfer the post_content of this page via DB edits, which is both risky and not guaranteed to work.

[benlk]

Still to address:

• why is the sticky nav showing up?