delete eplusout_err to prevent pyarrow overflow

[rajeee]

Fixes # .

Pull Request Description

Trying to fix postprocessing issue in GHPs run.
My current hypothesis is that because of too many E+ failures in a run, the dataframe's eplusout_err column has run out of space. This is a temporary fix.

Example error from @yingli-NREL

Checklist

Not all may apply

• Code changes (must work)
• Tests exercising your feature/bug fix (check coverage report on Checks -> BuildStockBatch Tests -> Artifacts)
• Coverage has increased or at least not decreased. Update minimum_coverage in .github/workflows/coverage.yml as necessary.
• All other unit and integration tests passing
• Update validation for project config yaml file changes
• Update existing documentation
• Run a small batch run on Kestrel to make sure it all works if you made changes that will affect Kestrel
• Add to the changelog_dev.rst file and propose migration text in the pull request

[joseph-robertson]

This is an issue with the eplusout_err strings being long, but not that the simulations are failing?

[rajeee]

This is an issue with the eplusout_err strings being long, but not that the simulations are failing?

Well, simulations failing is a problem too - but BSB should still be able to process the rest that don't have failures.

[joseph-robertson]

This is an issue with the eplusout_err strings being long, but not that the simulations are failing?

Well, simulations failing is a problem too - but BSB should still be able to process the rest that don't have failures.

As you mentioned GHPs, I'm curious what the simulation failures are.