Also do some minor cleanup to insertion of those field names

 * Set aria-label attribute on search input
 * Put anchor text directly into the DOM and not in the CSS

That issue was a dupe of 99852, but it's always better to
have multiple regression tests rather than one.

move 2 candidates into builtin candidate

having separate candidates for these isn't too helpful i think

r? types

…, r=compiler-errors

Make `deref_into_dyn_supertrait` lint the impl and not the usage

Proposed by `@compiler-errors` in rust-lang#89460 (comment)
r? `@crlf0710`

resolve: Don't use constructor def ids in the map for field names

Also do some minor cleanup to insertion of those field names.

Addresses a FIXME left in rust-lang#103578.

…, r=davidtwco

Add regression test for issue rust-lang#99938

That issue was a dupe of rust-lang#99852, and it got fixed since, but it's always better to have multiple regression tests rather than one.

closes rust-lang#99938

…-improvement, r=notriddle

Small accessibility improvements

From this [reddit post](https://www.reddit.com/r/rust/comments/z1gyz7/accessible_documentation/), I started to check a bit how to improve accessibility and how we could add test for it.

So these two fixes come from the use of the [pa11y tool](https://github.com/pa11y/pa11y). To make it work, I had to update its puppeteer version to the last one but otherwise it seems to be quite nice. I didn't fix all the errors it reported because they were about colors. To get the same result as mine, you can use this config:

```json
{
    "ignore": [
	"WCAG2AA.Principle1.Guideline1_4.1_4_3.G18.Fail",
	"WCAG2AA.Principle3.Guideline3_2.3_2_2.H32.2"
     ]
}
```

I think trying to improve accessibility is something we should definitely aim for. I'll try to integrate a tool to enforce this check (very likely `pa11y`) directly into the CI.

cc `@jsha`
r? `@notriddle`

…itespace, r=thomcc

Document split{_ascii,}_whitespace() for empty strings

doc change only