Jumper modeling

[jinningwang]

Describe the bug

Support the model Jumper (called Switch sometimes)
 
To Reproduce

Update data files and code for reproducing the error.

If you need to insert code inline, use a pair of triple backticks to format:

```python
Code goes here
```

Expected behavior

• Support Jumper model thus two Bus can connect together
• It would be good if the system matrices (PTDF, etc.) remain the same shape, but not sure if easy to do
• For valid Jumper (conditions check passed), actions to take when altering u: 1) update system matrices 2) anything else?

Desktop (please complete the following information):

• OS: [e.g. Windows]
• AMS version (please paste the output from ams misc --version)

pip packages (please paste the output from pip list)

Additional context

Proposed development efforts:

1. Add model Jumper
2. Add system connectivity check
3. Add action flow to allow automatic switching action (open -> close, close -> open)
4. Improve ANDES interface to support this
5. Improve MATPOWER file converter to support this

Reference:
ANDES - Jumper
pandapower - switch

[jinningwang]

@cuihantao Hantao, I summarized the Jumper development issues here and welcome your inputs.

Before actual development efforts, I need to figure out a doable plan.

[cuihantao]

Some of the pieces are already there in ANDES. There is a Jumper model and a connectivity check algorithm. Might need to be specific about the gaps.

[jinningwang]

Some suggestions received today: 1) lazy evaluation pattern, a status flag to indicate the topology change, and do the actual action when they are used, 2) keeping records can be a headache

[cuihantao]

Yeah, if you would like my comments, I will need to know some specifics.