…en the

geoemtry tag (defined by the BFC chain options and/or timestamp)
and the code which instantiates the geometry model.  The macro
is loaded / executed by St_db_Maker whenever GetDataBase("VmcGeometry")
is called.

This PR encodes the geometry tag inside of each database macro, rather than
using the ROOT interpreter's introspection capabilities to read
the tag from the filename of the currently executing macro.
This works well under ROOT 5 / CINT.  But I think the way that we
load macros in St_db_Maker confuses ROOT 6 / CINT.

The simplest solution is to encode the geometry tag within each
database macro.