Better data type for Linkage Errors and Artifact Problems?

@elharo says:

> I still think we're missing an abstraction here. We have problems of which there are several subtypes including missing artifacts and linkage errors. The linkage errors we don't have a class for. Instead we're storing them as an entry in the multimap.

https://github.com/GoogleCloudPlatform/cloud-opensource-java/pull/1135/files/a2dc1f7d9cd2ff0950b2c4d01e5b80c2018d52f5#r367607402

As of now
- Linkage errors are represented as `Multimap`
Many-to-many relationship between SymbolProblem and ClassFile.
- Artifact Problems are represented as `ArtifactProblem`
Example: non-resolvable artifacts in a dependency tree, when constructing a class path.

Start with the issue discussion and the referenced pull request diff, then compare the current Multimap representation with ArtifactProblem. Done should establish a clearly chosen abstraction that accounts for both linkage errors and artifact problems, with the distinction between their cases made explicit.

Escrita pelo modelo de indexação a partir do texto da issue.