[pkg/telemetryquerylanguage] Add the ability to use a logger in functions

[evan-bradley]

Description:

I've changed the TQL parsing functions to be methods on a struct that holds all common information necessary for parsing. Processors now instantiate the struct with a logger, which can then be injected into functions.

Link to tracking Issue:

Prerequisite for #9730.

Testing:

Unit tests were added, and manual tests were performed using modified functions.

Documentation:

I've added a note in the TQL readme aimed at function authors for how to get a logger.

[TylerHelmuth]

@evan-bradley Can you check the failing tests? I'll do a review tomorrow.

[bogdandrutu]

Pass "TelemetrySettings" not logger, since same argument can be done to record metrics.

Did not mean to block, but we need to make sure we get this right.

[TylerHelmuth]

Pass "TelemetrySettings" not logger, since same argument can be done to record metrics.

@bogdandrutu can you elaborate? Are you saying we should be able to pass the entire TelemetrySettings struct into functions?

[TylerHelmuth]

@evan-bradley I like the approach you've taken to introduce Logger. I think this is a great starting point towards refactoring the TQL to be more usable. @bogdandrutu I am still curious to hear more about your thoughts on passing the entire TelemetrySettings object.

[TylerHelmuth]

I like this implementation of Logger as it continues to allow the TQL to be generic to any telemetry, not only within the context of the Collector. If we want to pass in something like TelemetrySettings we could, but I don't think we would wrap it like this PR does for logger; it would be the literal TelemetrySettings type.

That change would be another step towards making the TQL specific to the collector, which I think is a conversation larger than this PR.

[TylerHelmuth]

@evan-bradley please address CI failures.

[evan-bradley]

Unfortunately I don't think the CI failures are related to any changes I've made, the errors call out deprecated function usage in some exporters. I rebased on the latest commit on main, but that doesn't appear to have solved it.

[dmitryax]

@evan-bradley PTAL #13753 to fix the linter issue

[dmitryax]

@evan-bradley please rebase

[evan-bradley]

@dmitryax Everything should be in order now.