Implement dependency detection for Maple files
At the moment, there is no tracking for interdependencies of Maple sources. Many of the files include
each other, which means that changes to one source file can silently break the generation of other functionals.
While it would be nice to have the regeneration tested automatically on the build farm, the discussions at the CECAM meeting led to the realization that dependency detection would partly solve this issue, and trigger the developer to regenerate any dependent C files.
I think the autogenerated Maple C files should contain a hash of all the employed sources, e.g. maple2c.py, and the whole dependency tree of Maple functional sources.