Consider adding an option for MobileFormatter to ignore version/signing on deserialization

[rockfordlhotka]

Although very risky and unsafe for a user, it may be possible for MobileFormatter to have an option to allow deserialization into a type of the same name/assembly where the version and signing information doesn't match.

The referenced discussion thread contains info about why this is risky and may lead to people having hard-to-find and hard-to-solve issues in their app.

---

Number 4: Apparently we are not using the SerializationInfo correctly. We add all of an object's properties using info.AddValue function regardless of if the value is a custom type or IMobileObject type or System type.

1. Add an option to turn on assembly/type matching somewhere in the CSLA options (default setting is off)
2. Change MobileFormatter to look at the matching options

Should just be those two.

Originally posted by @crazyfox55 in #3021 (comment)