FEDX-4020: Populate enclosing_range

[matthewnitschke-wk]

FEDX-4020

SCIP has a concept of enclosing_range

This is self described as "the nearest non-trivial enclosing AST node" which can be used to:

- Call hierarchies: to determine what symbols are references from the body of a function
- Symbol outline: to display breadcrumbs from the cursor position to the root of the file
- Expand selection: to select the nearest enclosing AST node.
- Highlight range: to indicate the AST expression that is associated with a hover popover

The main one I'm currently interested in is the first, using it as a way to determine which symbols are referenced from the body of a function

There's a long term goal of scip to be leveraged as a tool to determine impact of cleaning up deprecated functions. Using this data, we should be able to correctly estimate the total number of lines that could be cleaned up, including those referenced transitively by fully deprecated functions. The bulk of this work is implemented in cp_lab's scip-toolkit, but might see movement of a more public location

[matthewnitschke-wk]

enclosing_range is the first symbol that will commonly span multiple lines. as such our old getRange function wasn't built to handle this. That's what these updates are doing

[alanknight-wk]

@Workiva/release-management-pp

[rmconsole-wf]

+1 from RM