Prep for 24.1

[Myoldmopar]

Main change - assuming a more modern Python -- 3.12. For almost all users everywhere, this will not be a problem. For those people who want to use Python API to run EnergyPlus files which may also include Python Plugin files inside ---- they may want to change.

[Myoldmopar]

@jmarrec I re-ran EPTravisTester on my last E+ release where I just sorta reverted everything back to Python 3.8 and no ARM build from GHA. As you might see in the commit list, 8c7853e failed, and I was surprised. It wouldn't run the PythonPlugin file from an outside API call. I realized I had bumped TravisTester up to Python 3.12 to run these things, so I did a quick test. I pulled back down to 3.10 -- still failed. So for this niche application of Python API + Python Plugin File Inside EPlus, Pythons definitely MUST match.

I'm going to run one more test where I don't run the Plugin file, but use a different Python on GHA. I expect it to pass fine, but I"ll revert it back because I definitely want the API+Plugin test (for now).

[Myoldmopar]

Yep, it's all good. The only issue arises when a user wants to execute a Python Plugin enabled file through an API call into run_energyplus. In that specific case, the EnergyPlus-packaged-Python-interpreter has to match what the user is trying to call from outside.

I'm expecting this to be quite an uncommon application, so I think it's time to move on. I'm putting 3.8 back on GHA here and will move on.