refactor main core + initial setup for tap regulator input/output

[mgovers]

Relates to #74
Relates to #557

I needed this work for #557 but I deemed it out of scope of that PR, so I cherry-picked the changes and applied them here.

@nitbharambe maybe this will help you with #562 as well

[mgovers]

Quality Gate failed

Failed conditions 69.6% Coverage on New Code (required ≥ 80%)

See analysis details on SonarCloud

• most sonar cloud warnings are not new issues
• the ones that are, I deem out of scope of this PR because they would make the changes less obvious. may be future iterations.
• coverage relates to tap regulator input/output (to be tested in a separate PR), and fallback code like exceptions

[Jerry-Jinfeng-Guo]

Some are comments on existing codes prior to this PR.

[sonarcloud]

Quality Gate failed

Failed conditions
70.6% Coverage on New Code (required ≥ 80%)

See analysis details on SonarCloud

[Jerry-Jinfeng-Guo]

Not sure if any new tests are needed for the code coverage

[mgovers]

Not sure if any new tests are needed for the code coverage

not really necessary. there are no tests specifically about I/O currently in the first place. coverage will be reached once main model integration tests + validation tests are created

[mgovers]

BTW: pulling main into this branch is not required anymore due to the existence of the merge queue. it is recommended if the changes in main are big or conflicts are expected, but that's not the case here.

[Jerry-Jinfeng-Guo]

BTW: pulling main into this branch is not required anymore due to the existence of the merge queue. it is recommended if the changes in main are big or conflicts are expected, but that's not the case here.

That is noice. I was under the impression only conflicts between branchs in queue were addressed with this.

[mgovers]

BTW: pulling main into this branch is not required anymore due to the existence of the merge queue. it is recommended if the changes in main are big or conflicts are expected, but that's not the case here.

That is noice. I was under the impression only conflicts between branchs in queue were addressed with this.

that was the case until tony and I unchecked the Require branch up to date merge check 😬 Note that if there are conflicts, it will still require you to do the merge manually

[Jerry-Jinfeng-Guo]

BTW: pulling main into this branch is not required anymore due to the existence of the merge queue. it is recommended if the changes in main are big or conflicts are expected, but that's not the case here.

That is noice. I was under the impression only conflicts between branchs in queue were addressed with this.

that was the case until tony and I unchecked the Require branch up to date merge check 😬 Note that if there are conflicts, it will still require you to do the merge manually

So long story short: do it anyways...

[mgovers]

BTW: pulling main into this branch is not required anymore due to the existence of the merge queue. it is recommended if the changes in main are big or conflicts are expected, but that's not the case here.

That is noice. I was under the impression only conflicts between branchs in queue were addressed with this.

that was the case until tony and I unchecked the Require branch up to date merge check 😬 Note that if there are conflicts, it will still require you to do the merge manually

So long story short: do it anyways...

only if there's a good reason 😬