Combine remap & redirect info

[thomas-zahner]

It would be nice if the remaps could be printed before redirects. It would make all the remaps/redirects flow from left --> right.

Additionally we should consider combining them which further emphasises the order of operations:

Followed remap and 1 redirect: http://github.com/lycheeverse --[remap]--> http://rust-lang.org/lycheeverse --[301]--> https://rust-lang.org/lycheeverse

This might be difficult with the current Status::Redirected / Status::Remapped nesting. But it should be easier once #2097 is resolved.

Originally posted by @katrinafyi in #2094 (comment)

[mre]

That would be great. On that note, I found the remap/redirect output hard to parse visually. The lines are very long.

Was wondering if we should only show a shorthand format in normal mode and the full version in verbose mode:

So, in normal mode:

http://github.com/lycheeverse --> https://rust-lang.org/lycheeverse

or maybe

http://github.com/lycheeverse --> https://rust-lang.org/lycheeverse (after remap and redirects)

In verbose mode:

Followed remap and 1 redirect: http://github.com/lycheeverse --[remap]--> http://rust-lang.org/lycheeverse --[301]--> https://rust-lang.org/lycheeverse

I also thought about a tree-like output:

http://github.com/lycheeverse
└─[remap]─▶ http://rust-lang.org/lycheeverse
└─[301]──▶ https://rust-lang.org/lycheeverse

(It might be fine since the output is meant for humans anyway. If users want machine-readable output, they can use --format json.)

Related: #1926