Fix #5018 - C++ CLI: Calling a non existing method in a measure ends up with a crash and stack trace

Pull request overview

Fixes #5018
@kbenne saved the day by figuring out we could use the SWIG %feature("director:except")
I just implemented the error messages

[ ] TODO: Does this stuff need to be moved at a (much) higher level, so it applies to every SwigDirector we have, not just in Measure.i. Maybe in utilities/core?
- I think it isn't needed, because the only ruby/python stuff we call directly from C++ is the measure methods, but I could be wrong.
- @kbenne thoughts please

[ ] Model API Changes / Additions
[ ] Any new or modified fields have been implemented in the EnergyPlus ForwardTranslator (and ReverseTranslator as appropriate)
[ ] Model API methods are tested (in src/model/test)
[ ] EnergyPlus ForwardTranslator Tests (in src/energyplus/Test)
[ ] If a new object or method, added a test in NREL/OpenStudio-resources: Add Link
[ ] If needed, added VersionTranslation rules for the objects (src/osversion/VersionTranslator.cpp)
[ ] Verified that C# bindings built fine on Windows, partial classes used as needed, etc.
[ ] All new and existing tests passes
[ ] If methods have been deprecated, update rest of code to use the new methods

Labels:

[ ] If change to an IDD file, add the label IDDChange
[ ] If breaking existing API, add the label APIChange
[ ] If deemed ready, add label Pull Request - Ready for CI so that CI builds your PR

This will not be exhaustively relevant to every PR.

[ ] Perform a Code Review on GitHub
[ ] Code Style, strip trailing whitespace, etc.
[ ] All related changes have been implemented: model changes, model tests, FT changes, FT tests, VersionTranslation, OS App
[ ] Labeling is ok
[ ] If defect, verify by running develop branch and reproducing defect, then running PR and reproducing fix
[ ] If feature, test running new feature, try creative ways to break it
[ ] CI status: all green or justified