Error checking and displaying errors

[evaxliu]

We have the errors and error positions retrieved from parsing the model.
Next, we will display the errors through a red squiggly and also include hover information.

[evaxliu]

Managed to obtain errors from the parser and display. See below:

Now working on making the error's hover position more accurate and disabling regular hover for the positions with errors.

• Realized that there might not be regular hovers for the errors. I will probably isolate the error hover implementation from the regular hover implementation. I will have to figure out how to accurately determine the start and end position of these errors. (Returns the start column to the end of the line rather than having an accurate end column). See below:
  

[evaxliu]

Considering approaching error checking similar to vscode-antimony. We have grammar checks but not semantic ones. We can create an analysis.py type file in typescript which reads through the parse tree again and creates any error hovers based off of the rules defined in a types.py file which we should also create in typescript for this project.

[evaxliu]

https://tellurium.readthedocs.io/en/latest/antimony.html
Documentation of rules for antimony langauge

[evaxliu]

https://github.com/sys-bio/antimony/blob/develop/src/antimony.ypp

[Edih112]

https://github.com/sys-bio/antimony/blob/develop/src/enums.h
https://github.com/sys-bio/antimony/blob/develop/src/variable.cpp#L743

Working on carrying over all of the defined types in enums.h into the symbol tables.