Collect debloat data

[cesarsotovalero]

We'll need some data about the debloat results for each library:

• [ ] Write to file the # of methods removed
• [ ] Write to file the # of classes removed
• [ ] Write to file the # of dependencies removed
• [ ] Write to file the debloat execution time in seconds

[cesarsotovalero]

Once the debloat finishes, a debloat-report.csv file is written to the root of the Maven project. It contains the names of the classes and their usage type (UsedClass or BloatedClass). It also contains the name of the methods and their usage type (UsedMethod or BloatedMethod).

At the end of the execution, we write to a file debloat-execution-time.log the execution time of the plugin.

• [X] Write to file the # of methods removed:
• [X] Write to file the # of classes removed
• [X] Write to file the # of dependencies removed
• [X] Write to file the debloat execution time in seconds

The classes debloated per dependencies are written to a file (debloat-dependencies-report.csv) located in the root of the project. By the moment, this file has the following structure:

[dependency-name]
[usage-type], [class-name]
...

where <dependency-name> is the name of each dependency and usage-type is UsedClass or BloatedClass for each <class-name> that belongs to the dependency.