Context aware types in `ast_tools` schema

I wasn't sure about it since our types aren't context-aware so for less common type names you can have code like this:

// locally used type name.
type ReferenceId = usize;
#[ast]
#[generate_derive(ContentEq)]
struct X {
    span: Span,
    foo: ReferenceId,
}

Something like ReferenceId isn't that crazy to be used by someone who isn't aware of this and would mess up their equality checks for good(it is always true in this example).

What if we ignore the Span type name but use the name + type combo for the rest? Or we can actually look at the use statements and resolve the type names, I think it would also be a welcomed change in the oxc_regular_expression crate, Atom in regex means something else, and our atom is usually used there as use oxc_span::Atom as SpanAtom, But I had to change it back to Atom in the ast file to make the codegen recognize it.

Originally posted by @rzvxa in https://github.com/oxc-project/oxc/pull/5427#discussion_r1744774790

Read the ast_tools schema and the AST file referenced by the report, comparing how ReferenceId, Span, and Atom are recognized. Inspect the oxc_regular_expression use of Atom aliases; completion requires deciding and validating a context-aware type-resolution strategy, but the issue currently leaves that design choice open.