Added NegationContextAnalyzer processor and unit tests

[Piyush13y]

This PR fixes #3

Description of changes

• NegationContextAnalyzer processor added
• Unit tests added for the processor
• Medical pipeline example updated, by adding NegationContextAnalyzer to the pipeline

Possible influences of this PR.

Demo pipeline now uses the new processor and detects negation contexts for entity mentions.

Expected Output

[hunterhector]

1. I guess we want to lint the project with mypy, pylint and black to make it more standard before we merge this.
2. We will also need to set up test cases (and write test cases), like here.

[tanyuqian]

1. I guess we want to lint the project with mypy, pylint and black to make it more standard before we merge this.
2. We will also need to set up test cases (and write test cases), like here.

Sure. I'll update the workflow with more linting tools.

[Piyush13y]

@hunterhector Still unable to add @tanyuqian as a reviewer. It says I can add atmost 1 reviewer.

[hunterhector]

@hunterhector Still unable to add @tanyuqian as a reviewer. It says I can add almost 1 reviewer.

Add bowen in the future. I will get notified for the PRs anyway

[tanyuqian]

1. I guess we want to lint the project with mypy, pylint and black to make it more standard before we merge this.
2. We will also need to set up test cases (and write test cases), like here.

Pytest and documentation has been updated.
@Piyush13y Could you write unit tests for the components you developed? (mimic_reader and this negation analyzer)

[Piyush13y]

@tanyuqian I had already added test cases for NegationContextAnalyzer, and now I have added a test case for Mimic3 reader as well. However, there seems to be something broken with respect to pytest in the workflow I think, which gives errors in the CI pipeline. I am able to run these tests successfully on my local machine.

[tanyuqian]

@tanyuqian I had already added test cases for NegationContextAnalyzer, and now I have added a test case for Mimic3 reader as well. However, there seems to be something broken with respect to pytest in the workflow I think, which gives errors in the CI pipeline. I am able to run these tests successfully on my local machine.

@Piyush13y Could you double-check it is working from your end? like re-install forte/forte-wrapper/forte-medical and re-run? I got the same error message as the workflow here https://github.com/asyml/forte-medical/runs/5435388860?check_suite_focus=true#step:13:23
(ImportError: cannot import name 'MedicalEntityMention' from 'ftx.medical' (/opt/hostedtoolcache/Python/3.8.12/x64/lib/python3.8/site-packages/ftx/medical/__init__.py))

[Piyush13y]

@tanyuqian There were 2 issues raised in the CI pipeline initially, one was due to a stray test folder which, on deletion, fixed that problem.
The other one related to import statement is because this Forte-wrapper's PR is yet to be merged, which completes the namespace consistency story. I have run these tests with that PR and it works fine. There's some other issue which is failing a test on that PR which has blocked its merge for now. @hunterhector mentioned someone will be working on that but might take some time.