adds option to ignore uuid validation

[darwayne]

No description provided.

[TcM1911]

Thank you for your contribution @darwayne. I have hard time seeing how this feature would be needed given that it would allow objects with identifiers that are violating the specification. According to the spec, the identifier should be:

All identifiers, excluding those used in the deprecated Cyber Observable Container, MUST follow the form object-type--UUID, where object-type is the exact value (all type names are lowercase strings, by definition) from the type property of the object being identified or referenced and where the UUID MUST be an RFC 4122-compliant UUID RFC4122.

Do you have a usecase where you receiving STIX data from a producer that is not following the spec?

[TcM1911]

Link to spec for identifier: https://docs.oasis-open.org/cti/stix/v2.1/os/stix-v2.1-os.html#_64yvzeku5a5c