Claude review: rust: driver core: drop drvdata before devres release

[Claude Code Review Bot <claude-review@example.com>]

Patch Review

The critical C-side change that enables the entire series:

```c
 static void device_unbind_cleanup(struct device *dev)
 {
-	devres_release_all(dev);
 	if (dev->driver->p_cb.post_unbind_rust)
 		dev->driver->p_cb.post_unbind_rust(dev);
+	devres_release_all(dev);
```

The comment is updated from "Called after remove() and after all devres entries have been processed" to "Called after remove() but before devres entries are released."

This reordering is sound because, as the commit message explains, the driver's bus device private data is only accessible by the owning driver itself (drvdata() having been removed). The Rust-side comment update:

```rust
-        // `remove()` and all devres callbacks have been completed at this point
+        // `remove()` has been completed at this point; devres resources are still valid
```

This is well-justified and has appropriate reviews from both the Rust and driver-core maintainers.

### PATCHES 6-10: implement Sync for Device\<Bound\> (PCI, platform, auxiliary, USB, generic device)

Five small patches, each adding:

```rust
+unsafe impl Sync for Device<device::Bound> {}
```

for their respective bus types. The SAFETY comments correctly note that `Bound` is a zero-sized type-state marker and the underlying C struct is the same as `Normal`. These are needed because drivers storing `&'bound Device<Bound>` must be `Send`, which requires `Device<Bound>: Sync`. Straightforward and correct.

---
Generated by Claude Code Patch Reviewer