Avoiding issues with analyst data objects

[chrisr3d]

Using the different PyMISP helpers to add for instance an Attribute or an Object was causing issues when the given Attribute or Object was containing at least a Note, Opinion or Relationship. This was caused by the presence of the 'Note', 'Opinion' and 'Relationship' fields in every data layer inheriting from AnalysDataBehaviorMixin (including Notes, Opinions or Relationships themselves)

On the other hand, a Note, Opinion or Relationship information extracted from MISP is always contained in a 'Note', 'Opinion' or 'Relationship' fields, respectively.
A note extracted from MISP looks for instance like:

{
    "Note": {
        "uuid": "848337f8-781c-4998-8575-4fa4661b2a90",
        "object_uuid": "dbb85655-ec62-42b6-b05e-7085ee7af504",
        "object_type": "Attribute",
        "authors": "[email protected]",
        "created": "2024-10-03 14:13:56",
        "modified": "2024-10-03 14:13:56",
        "note": "Some random note",
        "language": "en"
    }
}

This makes the test for the presence of such fields mandatory when we want to use our Analyst Data information from MISP to created the equivalent objects in PyMISP.

With this PR, we reconcile both use cases with an additional contained parameter that is only used with the from_dict method of each Analyst Data object, set to True when we use add_note, add_opinion or add_relationship, in which case the analyst data information is obviously attached to another data layer.

This should fix #1306