[request] add dynamic config.json path support

[sarathm09]

No description provided.

[rahulbhargav]

@sarathm09 Can I work on this issue if no one else is working on it?
If so, can you provide some more information here?

[sarathm09]

@sarathm09 Can I work on this issue if no one else is working on it?
If so, can you provide some more information here?

This is a slightly tricky one.

As of now, before using vibranium in any system, there is this one task of initializing vibranium using a config.json. Though it has a lot of advantages like one time setup and having a global config, this imposes two limitations

1. The is no way to have project specific configurations
2. To run vibranium in some server (for example, as a jenkins job), the config.json needs to be maintained separately.

This issue is intended to remove this restriction. My proposal for this is as follows (please add your views)

1. If the directory from which vibranium is run has a config.json available, then pick that file instead of the global config else pick the global one
2. Add an option to specify the config file using some option like -c path/to/config.json and when specified, use that file instead of the one in the current directory or the global one.