Add support for Excel Macro invocation

[adamnagel]

When the current Excel wrapper runs, it sets the values of some cells (the parameters), then reads the values of some other cells (the unknowns). However, it is common for a spreadsheet to include macros. These are code or plug-ins that can be invoked to perform calculations. In these cases, the "output" values of the spreadsheets are not updated until the macro is invoked.

Here are some of the improvements that will need to be made to support macros:

• [ ] The test model needs to include a macro
• [ ] An optional constructor parameter allows a user to say "here's the macro you need to run to get updated values"
• [ ] When solve_nonlinear() runs, it needs to set the "parameter" cells, invoke the macro, wait for the macro to finish, and then read the "output" cells

[adamnagel]

@lattmann has some pointers to learn more: https://msdn.microsoft.com/en-us/library/microsoft.office.interop.excel._application.run.aspx https://msdn.microsoft.com/en-us/library/microsoft.office.interop.excel.applicationclass.run.aspx

[adamnagel]

Macro functions can accept arguments. For this first version, do not worry about supporting macros that accept arguments. Assume that the macro extracts the information that it needs from the cells of the spreadsheet itself.

[adamnagel]

As a bonus, it would be nice for the class to have a singleton function that takes a pointer to an Excel spreadsheet as an input, and returns the list of macros included with that spreadsheet. It could help users discover and identify them properly.