Support for lossy MachO parsing

[h33p]

Made it possible to parse MachO objects in less strict manner. However, default behavior is not changed. Therefore, there now is a new function parse_2 which accepts additional argument for lossyness.

Open questions:

• Is the default behavior intended? If not, parse_2 could be made private.
• Is parse_2 sufficient name, or should this be called something like parse_lossy?
• I made all of the commands work without fail in lossy mode, however, maybe some should fail?
• Should from_32_2 from_64_2 on Segment be exposed to the public? I currently have it pub(crate).

[h33p]

Thanks for review, finally got around addressing your comments. Please let me know if you need anything else.

[m4b]

@h33p CI is failing on rustfmt

[m4b]

once format fixed this is good to go

[h33p]

This should be good to go now @m4b

[m4b]

note: non-breaking

[m4b]

released in 0.8.1