feat: add transform processor as opt-in on custom build

[petrusdemelo]

Description

Add transform processor as opt-in for custom build using lambdacomponents.processor.transform tag.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: petrusdemelo / name: Petrus de Melo (625c229)

[serkan-ozal]

@petrusdemelo Shouldn't this new processor be added to default list here: https://github.com/open-telemetry/opentelemetry-lambda/blob/main/collector/lambdacomponents/default.go#L64?

[petrusdemelo]

@serkan-ozal I did not want to change the default build for the lambda collector. I just wanted to have it as an opt in option for custom build. But I can definitely add in the default build if that is the desire.

[tylerbenson]

I don't have issue with this as long as @serkan-ozal is ok with it. Need to rebase and resolve the conflicts though.

[serkan-ozal]

@petrusdemelo Ok, makes sense. I am OK with the PR. Could you please resolve the conflicts, then we can merge it.

[serkan-ozal]

@petrusdemelo any chance to rebase this PR?

[petrusdemelo]

@serkan-ozal yes, I had busy weeks. Will do it this weekend.

[serkan-ozal]

@petrusdemelo kindly bump on this

[ncorreia]

Hello, it would be really useful to be able to use a transform processor. Any updates on this? Thanks!

[petrusdemelo]

updated!

[wpessers]

@petrusdemelo I haven’t looked at this pr since review was done by other maintainers. Any reason for closing the pr? I see @RaphaelManke has shown interest in this feature in his comment. So if there’s still value in this I’m willing to reopen the PR and take a quick look myself and merge it if everything looks good.

[petrusdemelo]

@wpessers This branch has gone through several merge conflicts already, and since the PR has been open for quite a while, I haven’t been able to keep up with resolving each new conflict as they come up. If you’ll have time to take a look and merge it, I’d be happy to reopen the PR and fix the current conflicts.