Updating Template ModelMeasure

Still need to remove name section later and clean up header comments.
Adding $ to units
Fixing unit test
Merge branch 'MeasureImprovements' of github.com:NREL/OpenStudio into MeasureImprovements
Adding local On Demand user script

I also removed the BCL Space type and added an empty model template.
I'll update the new measure button on another commit.
renaming measure.rb to match class name

I did this because there will probably be more than one space type and
construction set generator. Specifically there will be one more specific
to residential constructions. It will live in the same sub-directory and
can share the same resources directory if needed.
Changing new button to use new vs. from template

Both new and new from template are still under the plugin file menu, but
the button has been wired up to a modified version of the new_openstudio
method in CommandManager.rb. Instead of taking the user default model,
it always uses the empty.osm file.  Then I run the user script to create
space types and construction sets.
Removing templates from plugin, fixing some issues with the space type generator wizard

[#60056158]
Issue warning if user cancels wizard
Add delay before calling user script so event processing is turned on

[#60056158]
Wiring button to wizard, and updating schedules

I hit an error testing with midrise, and realized the measure pre-dates
a fix to midrise thermostat that has been fixed in the standards repo.
Initial work on extending OSArgument
[#75135688]
Merge branch 'MeasureImprovements' of github.com:NREL/OpenStudio into MeasureImprovements
Initial addition of description, units, and model dependent to os arguments
Deprecating RubyUserScriptArgumentGetter for RubyUserScriptInfoGetter to pull more data out of the measure for use in the xml

[#75135688]
Merge remote-tracking branch 'remotes/origin/develop' into MeasureImprovements
Merge with develop fixed test
Test is finally passing!

[#75135688]
Able to set the default encoding but still can't require ruby gems.  I think Bugra is on the right path, I'll try creating some fake options and let the Ruby option parser do it all

@lefticus FYI
Changing interpreter initialization to rely on ruby_options since we don't want to reproduce all the spaghetti that occurs in that call

@lefticus FYI