Keeping SyntaNode's kind and parent kind for optimization

[eytan-starkware]

TL;DR

Cache syntax node kind to avoid database lookups.

What changed?

This PR optimizes the SyntaxNode struct by caching the node's kind and parent kind directly in the struct, rather than looking them up from the database each time they're needed. The changes include:

1. Added kind and parent_kind fields to the SyntaxNode struct
2. Modified the new_syntax_node function to accept and store the kind parameter
3. Updated the kind() method to return the cached value instead of looking it up
4. Updated the parent_kind() method to return the cached value
5. Modified node creation functions to pass the kind when creating new nodes

[reviewable-StarkWare]

This change is 

[eytan-starkware]

• Keeping SyntaNode's kind and parent kind for optimization #8515 : 2 dependent PRs (#8527 , #8578 ) 👈 (View in Graphite)
• Keeping SyntaxNode parent's data id for optimizations #8513
• Making Stable Syntax Pointers just a wrapper around syntax nodes #8501 : 1 other dependent PR (#8507 )
• Tracking SyntaxNode and interning through a tracked function #8489
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[orizi]

@orizi reviewed 2 of 2 files at r1, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @TomerStarkware)

[orizi]

@orizi reviewed 1 of 1 files at r2, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @TomerStarkware)

[orizi]

@orizi reviewed 1 of 1 files at r3, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @TomerStarkware)

[orizi]

@orizi reviewed 1 of 1 files at r4, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @TomerStarkware)

[graphite-app]

Merge activity

• Oct 28, 2:38 PM UTC: Graphite rebased this pull request, because this pull request is set to merge when ready.