Non-eponymous config files

Y configuration files are assumed to be eponymous (self-named) by default. This means that the name of the file will also be the primary ID for the information in the file.

Occasionally, multiple configuration information blocks might be defined in a single YAML non-eponymous config file.

When multiple configurations are defined in a single file, put the following meta information block in the configuration file, and then multiple distinct config blocks can be placed in a single configuration file.

_meta: { noneponymous: TRUE }

This syntax is found defining the fundamental bundles of the Beancount module and the default defined breakpoints in the Y module.