feat: add descriptive names to fingerprint tracing spans

Rename `create` → `create_post_run_fingerprint` and `validate` →
`validate_post_run_fingerprint` so they are identifiable in chrome-json
traces without relying on parent span context.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: branchseer

crates/vite_task/src/session/execute/fingerprint.rs

@@ -73,7 +73,7 @@ impl PostRunFingerprint {
     /// * `path_reads` - Map of paths that were read during execution
     /// * `base_dir` - Workspace root for resolving relative paths
     /// * `fingerprint_ignores` - Optional glob patterns to exclude from fingerprinting
-    #[tracing::instrument(level = "debug", skip_all)]
+    #[tracing::instrument(level = "debug", skip_all, name = "create_post_run_fingerprint")]
     pub fn create(
         path_reads: &HashMap<RelativePathBuf, PathRead>,
         base_dir: &AbsolutePath,
@@ -103,7 +103,7 @@ impl PostRunFingerprint {
 
     /// Validates the fingerprint against current filesystem state.
     /// Returns `Some(mismatch)` if validation fails, `None` if valid.
-    #[tracing::instrument(level = "debug", skip_all)]
+    #[tracing::instrument(level = "debug", skip_all, name = "validate_post_run_fingerprint")]
     pub fn validate(
         &self,
         base_dir: &AbsolutePath,