Extract IDs, Registries and Global into wgpu-core-remote

[sagudev]

Connections
Finally fixes #5121

Description
Move IDs, Registries and Global into wgpu-core-remote to be used by servo and firefox. This PR tries to achieve this with minimal changes, so it's mainly just moving stuff around and fixing imports. Future cleanups are noted in #5121 (comment)

Cargo and lib.rs are adapted from wgc. Because of tracing, we need to keep markers in wgc. To avoid complication with features and build scripts I removed some backend feature gated surface methods and one that is gated on tracing feature (if one needs them they are available in wgc::Device directly, but browsers do not use them anyway). So it's users are expected to depend on wgc directly for future selection. We use normal parking_lot instead of lock rank stuff as we we will remove them in the future anyway.

Testing
It compiles, but otherwise untested. We could implement wgpu custom backend using remoting, but maybe we can just trust that it works.

Squash or Rebase?

Squash

Checklist

• I self-reviewed and fully understand this PR.
• WebGPU implementations built with wgpu may be affected behaviorally.
• Validation and feature gates are in place to confine behavioral changes.
• Tests demonstrate the validation and altered logic works.
• CHANGELOG.md entries for the user-facing effects of this change are present.
• The PR is minimal, and doesn't make sense to land as multiple PRs.
• Commits are logically scoped and individually reviewable.
• The PR description has enough context to understand the motivation and solution implemented.

[teoxoy]

Great work!

[teoxoy]

Thoughts on removing ray tracing and presentation/surface functionality from the remote crate? Or more generally things that are not in the spec and also not useful to browser implementations. Shader cache might be interesting to keep - or not due to security concerns.

[sagudev]

Thoughts on removing ray tracing and presentation/surface functionality from the remote crate? Or more generally things that are not in the spec and also not useful to browser implementations. Shader cache might be interesting to keep - or not due to security concerns.

Yes, tho I planned that for follow ups to keep this PR with minimal decisions. We should also remove optional ids, and non ided global methods.