Refactor for QUBOTools.jl v0.10 -> v1

[pedromxavier]

This PR aims to reconsider a few design choices and settle the interface with a v1 milestone in mind.

This includes:

• Integrating QUBOTools.jl with the Graphs.jl interface (closes Integrate Graphs.jl interface #43): This allows for connectivity visualization recipes and piggybacking on the many metrics provided by Graphs.jl that could be used to analyze problems before solving them, as MQLib does.
• Defining a solver device & architecture interface (closes Create solver architecture & device interface #42): This moves the responsibility for this task from ToQUBO.jl to QUBOTools.jl and consolidates it as a first-class mechanism for building solver-dependent applications.
• Adding wrappers for visualization schemes (closes Add specialized wrappers for visualization recipes #41): Dispatching plot recipes directly on types limits the many different visualization settings that could be drawn from the same data. This also opens up the possibility of building a plot from different levels of abstraction using the same UI (JuMP/MOI/QUBOTools Model/SampleSet/QUBO Matrix).
• Define a clear standard for measuring solver execution time (closes How to measure time? #18, closes Set timing standard #22): Time spent in each step of the solution process has different implications on the final results when comparing solver performance. It is important to define at least a few standard time measures and leave room for measurements of arbitrary granularity to be stored.
• Enhance Stacked bar plot (closes Set different colors for stacked bars when plotting #31, closes Sort stacked bars in Solutions Summary by number of reads #39): It's hard to fully appreciate this plot when there are many reads. A few adjustments to the recipe settings could make it a lot better.
• Add metrics for measuring distance between solutions (closes Add function for computing Hamming distance between solution state vectors #37): Important to evaluate how far a solution is from the ground state in terms of bit flips.
• Sort out the MathOptInterface integration (closes Should we provide MOI support? #34, closes QUBOTools + MathOptInterface Wrapper for ToQUBO.jl and QUBODrivers.jl #45): QUBOTools was designed not to depend on MOI. Even though, we must provide a suitable set of resources for the integration to be carried out by the other packages in the QUBO.jl ecosystem.
• Add HDF5-based file format (closes HDF5 format #47): HDF5-based formats allow for fast serialization of complex data layouts, i.e., Model & SampleSet, with support for compression features.

[pedromxavier]

I will register the current commit as v0.10.0 without closing this PR. This will help propagating the changes across the entire environment, that already has a working chain from QUBOTools up to DWave, via QUBODrivers.