[FEATURE] Support for multiple Vision Excel versions

Jerry-Jinfeng-Guo commented 6 months ago

Vision 9.7 has introduced many changes to the exported excel sheet, which brings challenge to the existing VisionExcelConverter. Most significantly, UUID was introduced as the new id scheme. However, older versions like <9.6 are still extensively used by users who wish to take advantage of PGM as their compute core. To address this, we need to update our code base to accomdate the changes.

Here is the proposed temporary work-around:

Process the new excel sheets in a separate routine and make it backwards compatible\
- The argument is simple: this approach requires minimum changes to the code base and PGM internally do not depend on UUID's, and there is hardly any benefits in its current applications.

In the case that VisionExcelConverter is to be continued, here are the proposed solutions:

Open *.yaml configuration files as parameters to the converter. Currently one file is provided and users need to modify that versioned file or they need to go deep to the converter definition code to load any other configuration file. By making this a parameter, we could explicitly offload the whole *.yaml configuration task to users.
Treat old Number/Node.Number the same as GUID/Node.GUID and convert them all to strings in python. They are then collected to a map where each string key maps to an integer. This way, we combines the existing id scheme well with both Vision 9.7 UUID based scheme and Vision sub 9.6 number based scheme.
Extra care is needed trying to map terms: for instance, Vision 9.7 refer to N1 now as Grounding1. Many other such changes need to be mapped out accurately.