Pass message metadata to interpreter when parsing

[pheel]

Proposed changes:

• Currently a NaturalLanguageInterpreter's parse method receives message text, id and the tracker. This adds an optional argument for the message's metadata as well, and thus allows metadata to affect interpretation.

Status (please check what you already did):

• added some tests for the functionality
• updated the documentation
• updated the changelog (please check changelog for instructions)
• reformat files using black (please check Readme for instructions)

[sara-tagger]

Thanks for submitting a pull request 🚀 @tttthomasssss will take a look at it as soon as possible ✨

[pheel]

@federicotdn Would you mind having a look at this one? 🙏

[federicotdn]

Hey @pheel, could you share a bit more context on why you need the metadata for NaturalLanguageInterpreter.parse? Are you trying to do this on a custom subclass?

[pheel]

@federicotdn Exactly right! this is for a custom class, which makes use of contextual metadata sent over a socket to guide interpretation.

Right now an incoming message m's metadata is written into the tracker after interpretation, at the same time as the parse data that results from interpretation. Since NaturalLanguageInterpreter is given access to the pre-interpretation tracker state, containing all information about messages that came before m, I think it should have access to at least as much information about m itself.

[federicotdn]

Ok! Looks good. You you mind merging master into it? I think there might be some merge conflicts.

[federicotdn]

Thanks!