Code Versioning for fpy_auxiliary

[rosenbrockc]

Currently, when a unit test requires the autoclass feature, fortpy compiles the auxiliary module automatically, but only if the code version has changed. But what defines the code version? The template version number shipping with fortpy will hardly ever change, but when it does, then the code knows to recompile. However, when the user's version changes, we have no idea so the newest versions of the auxiliary module don't necessarily get copied over.

We could have it recompile and copy auxiliary every time a test is run to be safe, but that is really wasteful because most user types don't change very often in a code's development cycle. We could have the user set the version number in a separate file, but that can be irritating for them. Maybe it is best to have a flag in runtests.py that forces a recompile and copy. Then, if the user is having issues, they could force a re-copy and it would work.