fix(cli): relative file path formatting (#5565)

[mdevils]

Summary

Here is a potential fix for the issue #5565

Closes #5565

Test Plan

Here is new output format:

src/routes.tsx:128:35 lint/correctness/useHookAtTopLevel ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ✖ This hook is being called from a nested function, but all hooks must be called unconditionally from the top-level component.

[arendjr]

I'm afraid that failing test indicates a regression...

[ematipico]

Unfortunately, this approach doesn't work. There are a few things to keep in mind:

• diagnostics aren't - and shouldn't - be aware of the concept of "relative" and "absolute" paths.

• File paths are provided to the diagnostics at the source, when we create them, meaning we should avoid as much mutation as possible by the time we print them.

• Some diagnostics are created during the crawling of the file system. These diagnostics say "Biome can't handle this file extension". This is the struct:
  

  biome/crates/biome_service/src/diagnostics.rs

  Lines 317 to 321 in 8227773

  	pub struct SourceFileNotSupported {
  	file_source: DocumentFileSource,
  	path: String,
  	extension: Option<String>,
  	}

  We throw this error in a couple of places, and the tricky one is when we use this function, because it's a pure function used in few palces:
  

  biome/crates/biome_service/src/diagnostics.rs

  Lines 427 to 434 in 8227773

  	pub fn extension_error(path: &BiomePath) -> WorkspaceError {
  	let file_source = DocumentFileSource::from_path(path);
  	WorkspaceError::source_file_not_supported(
  	file_source,
  	path.clone().to_string(),
  	path.clone().extension().map(|p| p.to_string()),
  	)
  	}

[ematipico]

Why was this changed? Both conditions must be checked

[ematipico]

I'm not sure I understand this change. Can you explain it?