feat: range metadata

[doorgan]

Adds a :range property to the nodes metadata

The performance impact of this is detailed in expert-lsp/expert#651
TL;DR I expect this to help quite a bit when indexing large codebases in Expert, but I think I'm getting limited by IO in that project so I can't be 100% confident on that. Profiling shows significant improvements though, but it's not the practical reality I experience.

I decided on this format for the range metadata: %{start: {line, column}, end: {line, column}. The rationale is that keyword ists are really slow to read in a very hot path, while maps have better random access. line/column pairs are tuples for the same reason. {start_line, start_column, end_line, end_column} didn't provide much of an improvement over maps in what I could measure and the ergonomics were terrible(no nice way to get only the start or only the end of a node).

This also adds a new dedicated ranges test file which is mostly a translation of the Sourceror ranges test suite to verify parity/precision. The diff on the spitfire tests is mostly updating assertions to ignore the Spitfire specific metadata when comparing against Elixir's own AST

[doorgan]

Despite what profiling initially shows, it does not make a significant difference indexing real projects in expert