rustdoc: List of issues related to Markdown input files

[fmease]

I didn't feel like opening 3 2 GH issues for these niche issues, so here's a single one.

• Given a Markdown input file and --markdown-css file.css, the depinfo (--emit=depinfo -Zunstable-options) doesn't list file.css
• Given a Markdown input file and --markdown-css file.css, the generated HTML document contains <link rel="stylesheet" href="file.css"> but that path won't resolve unless you set -o. / --output-dir=. since it doesn't properly account for the output directory (which is doc/ by default)
• Given a Markdown input file and --emit=html-static-files or --emit=dep-info or --emit=html-static-files,dep-info, we still emit a non-static HTML file, e.g, doc/file.html (which should only be emitted if --emit contains html-non-static-files which it implicitly does by default)

[notriddle]

Wait, hold on.

If the contents of the CSS file change, the build system doesn’t need to re-run rustdoc. It only needs to re-run rustdoc if the name of the CSS changes.

We shouldn’t include CSS hotlinks in the dep-info at all, do we?

[fmease]

Oh, you're absolutely right!