Improve logging around surface creation

[Wumpf]

Connections

• Split out of Fix Vulkan surface capabilities being advertised when its query failed.  #6510
• tiny part of INFO-level logging is too verbose #3206

Description

• demoted a few info messages to debug
• request_adapter is more talkative about its decisions in debug log messages now
• add a doc line to RequestAdapterOptions::compatible_surface, this duplicates what we already write on wgpu's request adapter, but better to request this weirdness where it's needed!

Testing
ran hello_triangle and looked at things

Checklist

• Run cargo fmt.
• Run taplo format.
• Run cargo clippy. If applicable, add:
  • --target wasm32-unknown-unknown
  • --target wasm32-unknown-emscripten
• Run cargo xtask test to run tests.
• Add change to CHANGELOG.md. See simple instructions inside file.

[nical]

Looks good to me but I remember @jimblandy mentioning a while back that having some of the adapter related logging in firefox (which filters out anything below info and it's tricky to change because reasons) was important.

[teoxoy]

We should probably use the api_log! macro.

[Wumpf]

to be clear, I'd really prefer having those logs in debug :) (telling users to run a program with RUST_LOG=debug is a common thing I do when encountering issues rendering issues)
so api_log would mean I don't have them on trace unless I enable the feature which pushes it to info