Parse user specified ontology file

[qinzzz]

This PR handles the parameter onto_file_path in DataStore's init method.

Description of changes

If onto_file_path is not None, build tyoe_attribute dictionary based on the provided ontology file.

Possible influences of this PR.

Describe what are the possible side-effects of the code change.

Test Conducted

test_check_onto_file in data store test.

[codecov]

Codecov Report

Merging #692 (0a75ae2) into master (5e966b9) will increase coverage by 0.05%.
The diff coverage is 96.66%.

@@            Coverage Diff             @@
##           master     #692      +/-   ##
==========================================
+ Coverage   80.35%   80.40%   +0.05%     
==========================================
  Files         253      253              
  Lines       19315    19358      +43     
==========================================
+ Hits        15520    15565      +45     
+ Misses       3795     3793       -2     

Impacted Files	Coverage Δ
forte/data/data_store.py	82.55% <95.65%> (+1.62%)	⬆️
forte/common/constants.py	100.00% <100.00%> (ø)
forte/data/ontology/ontology_code_const.py	100.00% <100.00%> (ø)
tests/forte/data/data_store_test.py	95.46% <100.00%> (+0.10%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5e966b9...0a75ae2. Read the comment docs.

[hunterhector]

try to reuse the ontology code generator

[hunterhector]

In additional to the comments, there are a few more general steps missing:

1. We always need to associate a PR with an issue for tracking purposes.
2. Need to resolve conflicts.

[hunterhector]

let's pass the CI?

[hunterhector]

@mylibrar

[hunterhector]

For this PR let's focus on making the test case covering what we want.