fix(site): confirm destructive interactions!

Why oh why wasn’t this done in the first place? An almost unforgivable sin. There should never ever exist any destructive interactions that doesn’t require a confirmation before its carried through.

Solved now anyhow.
docs(version): preparing for version 0.4.4
test(parser): testing consistent mention parsing
fix(dependencies): updated microformat-node etc
test(parser): matching parsed result of templates
test(parser): ensure resolving of relative URL:s
refactor(parsing): set a microformat-node baseUrl
fix(parser): fixed exception on empty summary
feat(parser): parse interaction type of mentions
fix(api): whitelist the properties of mentions
refactor(embed): linted the embed script
feat(embed): add cutting-edge embed with facepile

A new experimental cutting-edge version of the embed, that will change frequently and thus should be expected to break and therefore not really used live unless one watches this project very closely, has been added and with it a new Facepile feature that separates out all like/repost interactions from the rest and only includes such interactions if they explicitly liked or reposted something matching the query of the embed (often the page the embed is soon)

One uses this new embed by adding a new `version` query parameter thats set to ”cutting-edge” and if one doesn’t want a facepile because one might be building eg a mentions feed, then one can also add a new `nofacepile` query parameter to include the likes and posts like they used to be included.
docs(version): updating changelog
docs(api): documented the API:s and embed options