Update topbar to work without jQuery Sizzle

The `> ul` selector is not valid for `querySelectorAll`. If I'm using a minimal jQuery build, `foundation.topbar` fails. This change uses `children` and `filter` to accomplish the same effect. As this is only running at init, I doubt there would be any performance implications.
Don't fail installing rAF polyfill if jQuery.fx isn't present

When using a minimal jQuery build, `jQuery.fx` might not be available. This patch checks to make sure the namespace exists before trying to overwrite the functionality.
I started to try and fix assuming tooltips were on mobile if the browser registered touchstart, ended up making all tooltip settings per tooltip, as well as make tooltips behave based on event type, not on browser registering touchstart
Clean up the code a bit. Should allow you to switch to a mouse based input type even if you opened it using touchstart. Clicking on the data-tooltip element via touchstart will now close it so you don't have to click on the tooltip itself
Better handling of switching between touch and mouse events
A little bit of cleanup.
Update foundation.interchange.js to work with background-image

When a tag(not an image tag) has a data-interchange attribute containing an image path it will set a background-image on element instead of trying to replace the innerHtml.
Should fix #4053

Don't use this.outerWidth since this doesn't reference the element the tip is supposed to be pointing at.
Fix bug Issue #3630

https://github.com/zurb/foundation/issues/3630
Update foundation.interchange.js
Fix to prevent background-image to change on every resize if not necessary
Adding documentation on interchange with background-image.
Don't require accordion sections to be siblings.

This will allow accordions that have their sections separated into
different block-grid areas.
Improve documentation.
Fix orbit bullets not lining up horizontally.

Observed: orbit bullets are lined up vertically, with `display: block` style set instead of `display: inline-block`. This is because the styles of the `li` element of `.orbit-container` overwrites `li` element of `.orbit-bullets`.
Fix: Add additional specificity to `.orbit-container li` as `.orbit-container ul li` so that it applies only to the images of the Orbit, not to the bullets.
Update normalize.css to the latest 2.1.3 version

As seen on http://necolas.github.io/normalize.css/ the version 2.1.3 is the latest for now, so it's time to update.
Pass along dropdown and target references for opened/closed event in Dropdowns
Add "slide_number" and "next_slide_number" parameters to orbit's before-slide-change event and callback
Update foundation.orbit.js

Since data-orbit-link does work on non-<a> elements when it comes to controlling the slideshow, the same should be true for updating the active link status for those elements (alternatively both should fail on non-<a> elements). Either way, it should be consistent. This proposal does the former, since I find it to be useful and can't see a reason why not.
Automatically generate visibility classes

Replaces most of the visibility classes with a mixin that simplifies
the process of adding or removing breakpoints and their associated
visibility classes. Resulting CSS is comprehensive without containing
any extraneous or nonsensical classes, and is far less error-prone.