refactor: add inline function step to replace functions after parsing

[sgulseth]

Description

Adds a temporary step when parsing functions. We first gather all the function calls and parses them as InlineFunctionCall, when we have gathered all the calls we replace them.
This is to support custom functions, where order of calls doesn't matter, so we first need to know all function definitions before we can replace them.
See #309 for more context on custom function implentation.

Most of the changes are due to changing the expression builder method

What to review

I introduced a walk method to walk the AST, however this might be slow on very large queries. Is this an issue? 🤔 Another approach would be to store a reference(or similar) to each InlineFunctionCall, and then only replace the node's values.

Testing

Did not add any tests, as this doesn't change any behavior and only refactors to be compatible with custom groq functions

[sgulseth]

This change is part of the following stack:

• refactor: add inline function step to replace functions after parsing #308 ◀
  • feat(parser): add support for parsing and replacing custom functions #309

_{Change managed by git-spice.}

[judofyr]

Some alternatives:

(1) Just remove the func definition during parsing and rather do it during execution:

export interface FuncCallNode extends BaseNode {
  type: 'FuncCall'
  namespace: string
  name: string
  args: ExprNode[]
}

(2) Make it optional:

export interface FuncCallNode extends BaseNode {
  type: 'FuncCall'
  func?: GroqFunction
  namespace: string
  name: string
  args: ExprNode[]
}

It's sort-of an optimization that we detect the function at parse time. It's probably not really worth it?

[sgulseth]

Wouldn't that be a breaking change though?