bugfix(formatter): Made cairofmt::skip work properly for additional items. - #10220

Summary

Extends #[cairofmt::skip] support to TraitItemType, TraitItemConstant, TraitItemImpl, and ItemMacroDeclaration nodes. Previously, applying #[cairofmt::skip] to trait associated types, constants, or impls, as well as macro declarations, had no effect because these syntax kinds were not handled in QueryAttrs. The attribute lookup now returns their attributes correctly, allowing the formatter to respect the skip directive.

Type of change

Please check one:

• Bug fix (fixes incorrect behavior)
• New feature
• Performance improvement
• Documentation change with concrete technical impact
• Style, wording, formatting, or typo-only change

Why is this change needed?

#[cairofmt::skip] was silently ignored when placed on trait associated types (type Bar), trait associated constants (const FOO: i32), trait associated impls (impl Baz: MyTrait), and macro declarations (macro my_macro { ... }). This was because the QueryAttrs implementation for SyntaxNode did not include match arms for these syntax kinds, so their attributes were never surfaced to the formatter.

What was the behavior or documentation before?

Applying #[cairofmt::skip] to trait item types, constants, impls, or macro declarations had no effect — the formatter would reformat those items regardless of the attribute.

What is the behavior or documentation after?

#[cairofmt::skip] is now respected for TraitItemType, TraitItemConstant, TraitItemImpl, and ItemMacroDeclaration, preserving their original formatting as written.

Related issue or discussion (if any)

N/A

Additional context

Test cases covering all four newly supported node kinds have been added to fmt_skip.cairo and its corresponding expected output file.