rustdoc: update pulldown-cmark to 0.10

[stepantubanov]

Updated from 0.9 to 0.10.

[rustbot]

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @GuillaumeGomez (or someone else) some time within the next two weeks.

Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (S-waiting-on-review and S-waiting-on-author) stays updated, invoking these commands when appropriate:

• @rustbot author: the review is finished, PR author should check the comments and take action accordingly
• @rustbot review: the author is ready for a review, this PR will be queued again in the reviewer's queue

[rustbot]

The list of allowed third-party dependencies may have been modified! You must ensure that any new dependencies have compatible licenses before merging.

cc @davidtwco, @wesleywiser

These commits modify the Cargo.lock file. Unintentional changes to Cargo.lock can be introduced when switching branches and rebasing PRs.

If this was unintentional then you should revert the changes before this PR is merged.
Otherwise, you can ignore this comment.

[GuillaumeGomez]

cc @notriddle

[notriddle]

I don’t think we can merge this yet.

pulldown-cmark/pulldown-cmark#864 has not been released yet. It could also use a lint to mitigate some of the other regressions found in #121659

[stepantubanov]

@notriddle I see, that makes sense, thanks! Should I close this or keep it open until we can update?

[rustbot]

Some changes occurred in src/tools/clippy

cc @rust-lang/clippy

[bors]

☔ The latest upstream changes (presumably #122968) made this pull request unmergeable. Please resolve the merge conflicts.

[Dylan-DPC]

@stepantubanov if you can resolve the conflict with the lock file and mark this as ready for review we can push this further

[bors]

☔ The latest upstream changes (presumably #124213) made this pull request unmergeable. Please resolve the merge conflicts.

[notriddle]

#127127 makes this outdated.