Global state views in PhasorDynamics SystemModel

[lukelowry]

Description

This PR updates PhasorDynamics so buses and components use their slices of the SystemModel state vectors directly. This removes the local state copy path and keeps component accessors consistent with the integrator-updated system state.

Partially addresses #96. Related to #145.

Proposed changes

• Added StateVector support so GridElement can own standalone state or alias SystemModel state.
• Updated SystemModel allocation to bind each bus/component to global state and verify element sizes remain fixed.
• Updated Enzyme call sites to use the explicit yData() accessor for live state pointers.
• Added a PhasorDynamics system test for element/system state aliasing.

Performance was measured with application/PhasorDynamics/PDSim using the app-reported Complete in time. Each row reports the median of 3 trials after rebuilding PDSim on the corresponding branch.

Case	develop (s)	This branch (s)	Improvement
Hawaii	0.201302	0.165187	17.9%
NewEngland	0.272596	0.220406	19.1%
Illinois	0.664262	0.592922	10.7%
WECC	1.203380	1.045540	13.1%
Texas	9.063860	7.515690	17.1%

Checklist

• All tests pass. (except the known PE failure)
• Code compiles cleanly with flags -Wall -Wpedantic -Wconversion -Wextra.
• The new code follows GridKit(TM) style guidelines.
• There are unit tests for the new code.
• The new code is documented.
• The feature branch is rebased with respect to the target branch.
• N/A: no CHANGELOG.md update is needed for this internal PhasorDynamics state-storage change.

Further comments

This work was motivated by the addition of IEEEST stabilizers: adding 333 stabilizers to the Texas case dramatically reduced performance, and this change removes avoidable state-copy overhead in PhasorDynamics system evaluation.

This is not intended to be the final state-vector API design. The cleaner long-term solution would be to update Evaluator so state and residual accessors expose non-owning vector views instead of requiring owned std::vector storage, e.g.

virtual VectorView<ScalarT> y() = 0;
virtual VectorView<ScalarT> yp() = 0;
virtual VectorView<ScalarT> residual() = 0;

This PR keeps the change local to PhasorDynamics while removing the current copy path.

[pelesh]

Blocking this PR until Jacobian implementation in PhasorDynamics is refactored to eliminate deprecated Matrix_COO object.

[pelesh]

@lukelowry, please take a look at vector class in Re::Solve. This is something we need to add to the GridKit/LinearAlgebra directory and use it in place of StateVector class you added to GridElement.hpp. I'm afraid StateVector class may not be portable as implemented in this branch.

[lukelowry]

@pelesh Are you suggesting Re::Solve become a dependency? or use as inspiration for our own Vector class? I moved and refined the implementation as you suggested, but a full implementation would be a larger change. I added a comment in the code for the future work we would need to do.

[pelesh]

@pelesh Are you suggesting Re::Solve become a dependency? or use as inspiration for our own Vector class? I moved and refined the implementation as you suggested, but a full implementation would be a larger change. I added a comment in the code for the future work we would need to do.

See #418

[PhilipFackler]

I think this is great as-is. Replacing this Vector class with the Re::Solve version in a later PR would be pretty straightforward.