Integrity: Added new event 'error[name="config-mismatch"]'

 - [x] Integrity: Added new event 'error[name="config-mismatch"]'
 - [x] Security: Also added filtering to only honor FlashVars. Supersedes #336.
 - [x] Also revved version to 2.2.0-beta.3

Fixes #379
Fixes #164
Closes #336

Still don't have FlexUnit tests in place yet (:sob:), so I'm uncertain if this covers 100% of security holes previously identified in #164 and #336 by @masatokinugawa. However, I've also combined it with a new technique of using `ExternalInterface` to call out and interrogate the DOM for the actual FlashVars.

This DOM interrogation for FlashVars helps both with security (#164, #336) and in preventing weird browser caching issues for FlashVars (#379).

cc: @jonrohan @mjtko @nodesocket @masatokinugawa @ptoomey3 @jnewland @mastahyeti &rarr; _Please review!_


I don't have an argument as to why it would be beneficial to expose the whole of `metadata` or, equally, a strong argument against other than that it's preferable to keep any exposed information useful.  If there are clear benefits to exposing more of `metadata`, that'd be fine too, but this seems sufficient to me.