Enhance recoverable_problem to require/allow a description of what the problem is

Apport supports filing RecoverableProblem reports. These are not crashes, although they do still get created as *.crash.

I'd like to suggest we do 2 things:

1) enhance /usr/share/apport/recoverable_problem to require some sort of human-readable description of what the problem is since currently it is entirely up to the caller to set some key/value pairs. An example from a recent RecoverableProblem report:

<snip>
ProblemType: RecoverableProblem
DuplicateSignature: icon-path-unhandled-com.ubuntu.notes_notes_1.4.235
</snip>

This makes perfect sense to the a very small number of folk, but makes no sense to anyone else :) For interested readers the above actually means, "an icon exists that is not configured".

How about we add an option to recoverable_problem so that it would/could get called as:

/usr/share/apport/recoverable_problem --description <mandatory_description_of_problem> key=value [key=value...]

/usr/share/apport/recoverable_problem "an icon exists that is not configured (<path_to_icon>)" \
    DuplicateSignature icon-path-unhandled-com.ubuntu.notes_notes_1.4.235

That would then generate a report containing in this case:

ProblemType: RecoverableProblem
RecoverableProblemReason: "an icon exists that is not configured (<path_to_icon>)"
DuplicateSignature: icon-path-unhandled-com.ubuntu.notes_notes_1.4.235

2) Write RecoverableProblems to *.info files rather than *.crash. I appreciate that this could require quite a bit of work since it would require changes to atleast apport and whoopsie but since these reports are not crashes, I do not think the file should end with .crash as that looks alarming and is strictly incorrect.