Enhancement Request - Provide additional Templates of ranges

[TheLawsOfChaos]

The configure option of attack_range.py contains some of the options and going through the actual code showcases many other good options that are available. Is it possible to provide some other example .yml configs of ranges?

Or allow for passing in our own default .yml to use (instead of always starting with attack_range/configs/attack_range_default.yml. Or making a second layer of defaults, similar to using splunk apps to layer together multiple configs into a single one.

Use case for allowing us to provide our own 'default' instead of or in additional to yours:

If I'm working in an environment, I would love to configure the general section once, and have all future iterations use that where I only define the machines I want to create etc for each individual attack range. i.e. if all of my ranges will be using the same AWS configuration, or the same local/vagrant etc I shouldn't have to define that each time, I could instead pass it my 'default' to start with.