please support the `.ovirtci` directory as a fallback to the `automation` directory.
In cases where multiple CI systems are used, it is heplful to have each's CI tool's configuration in a directory containing the vendor or so string.
Slightly changed from the original request, its not mandatory we'll call it '.ovirtci', but just something that wont be too generic as 'automation', but rather named after the std-ci framework.
So we'll need to find a name for it.
Adding as a blocker for this because it tracks our current efforts to make a new STDCI configuration format where the use of the 'automation' dir can be avoided.
this can probably be closed now that V2 supports multiple naming options
STDCI V2 now allows full customization of where scripts and configuration files reside.