In order to let users circumvent the plugin loading mechanisms for
loading plugins specified in the `required_plugins' blocks, we add a new
`path' attribute to the plugin specifiers.
Specifying this attribute makes it so that loading the plugin
circumvents completely the checks in place for a required plugin
(version, source), and forcefully loads the plugin from the specified
path.
That being said, this is not a reliable long-term solution for this kind
of problem, as it makes it harder/impossible to share the template, as
the path must resolve in order for the build to proceed, and this is
environment-bound.
Lucas Bajolet
e5f531166f