Show beets' recommendation when prompting the user

[andzno1]

It would be nice to show the recommendation for a match when prompting the user for an action. Right now, when the user is being prompted (e.g. in timid mode) something like this is being displayed:

 Match (96.1%):
  Bela B. - Bingo
  ≠ missing tracks, tracks, label
  MusicBrainz, CD, 2006, DE, BPX 1992, BPX 82876836652, Limited Edition
  https://musicbrainz.org/release/7c31c8d9-dbd4-4440-9329-0f20d5027ed7
  * Artist: Bela B.
  * Album: Bingo
     ≠ (#1) B-Vertüre (2:27) -> (#1) B-Vertüre (1:20)
     ≠ (#7) Was Ist Nur Los ...? (2:33) -> (#7) Was ist nur los …? (2:33)
     ≠ (#8) 1. 2. 3. ... (3:00) -> (#8) 1. 2. 3. … (3:00)
     ≠ (#13) Hab Keine Angst (3:58) -> (#13) Hab keine Angst (3:58)
     ≠ (#17) Traumfrau again (1:11) -> (#17) Traumfrau Again (1:11)
Missing tracks (1/18 - 5.6%):
 ! Theme From Bingowings (#0) (1:07)
➜ Apply, More candidates, Skip, Use as-is, as Tracks, Group albums,
Enter search, enter Id, aBort?

For a configuration like this

match:
  max_rec:
    missing_tracks: low
    unmatched_tracks: low

it would be really nice to have additional information on beets' recommendation, e.g.:

- Match (96.1%):
+ Match (96.1%, recommendation 'low', downgraded from 'strong', reason: missing tracks):
  Bela B. - Bingo
  ≠ missing tracks, tracks, label
  MusicBrainz, CD, 2006, DE, BPX 1992, BPX 82876836652, Limited Edition
  https://musicbrainz.org/release/7c31c8d9-dbd4-4440-9329-0f20d5027ed7
  * Artist: Bela B.
  * Album: Bingo
     ≠ (#1) B-Vertüre (2:27) -> (#1) B-Vertüre (1:20)
     ≠ (#7) Was Ist Nur Los ...? (2:33) -> (#7) Was ist nur los …? (2:33)
     ≠ (#8) 1. 2. 3. ... (3:00) -> (#8) 1. 2. 3. … (3:00)
     ≠ (#13) Hab Keine Angst (3:58) -> (#13) Hab keine Angst (3:58)
     ≠ (#17) Traumfrau again (1:11) -> (#17) Traumfrau Again (1:11)
Missing tracks (1/18 - 5.6%):
 ! Theme From Bingowings (#0) (1:07)
➜ Apply, More candidates, Skip, Use as-is, as Tracks, Group albums,
Enter search, enter Id, aBort?

That way

• users could see why they are being prompted in non-quiet mode, and
• when running in timid mode, users can see what beets would have done if it wasn't running in timid mode. This would help to understand changes made to the configuration and how it would impact beets' decision making.