init script revamping

[Grummfy]

Hi, today we got a 'atoum --init' to initialise a configuration file, perhaps we can do more?

Like asking question about:

• some extension (telemetry, reports, ...),
• path to test unit directory,
• enabling or not the path coverage for the test,
• if we use composer or a custom autoloader,
• ...

What do you think about this? It could be very helpful to have it?

[Grummfy]

@atoum/contributors I would like to ave feedbacks on it. I think it's not a complex one and it could be easily done by someone else than the core contributors, but we just need to speak a bit about it.

[kao98]

Indeed I like the idea :)

[Grummfy]

So we get several way to act:

• update existing command with file up to date, about autoloader, bootstrap & configuration & add a new command for the interactive part
• update the existing one with interaction and a possibility of disabling it by providing response to questions

So the command would ask:

1. Create an autoloader, mostly useless if you use composer [y/N]?
2. Create a boostrap file [y/N]?
3. Create a configuration file [y/N]?

If create a config file:

1. Path to unit test directory: [path]
2. Activate path & branch & test coverage [y/N]?
3. Activate some extension [y/N] ?
   • telemetry [y/N]
   • reports [y/N]
   • autoloop [y/N]
   • ruler [y/N]