Signozlogspipelineprocessor: use own copy of stanza operators

[raj-k-singh]

Brings in copies of stanza pieces relevant to logs pipelines from opentelemetry-collector-config at processor/signozlogspipelineprocessor/stanza/

Bringing over pieces of stanza will give us the ability to modify anything and everything as needed to achieve our goals with logs pipelines

Almost all of the files in this PR have been brought in as is with no/minimal modifications and have a comment stating the same in their 1st line

contributes to SigNoz/signoz#5894 and SigNoz/signoz#4444

[srikanthccv]

Excluding the code that has been brought in as is, I see a major change as signozlogspipelineprocessor/stanza/operator. Can you help me understand what is the difference b/w processor/signozlogspipelineprocessor/stanza/operator and opentelemetry-collector-contrib/pkg/stanza/operator?

[raj-k-singh]

Excluding the code that has been brought in as is, I see a major change as signozlogspipelineprocessor/stanza/operator. Can you help me understand what is the difference b/w processor/signozlogspipelineprocessor/stanza/operator and opentelemetry-collector-contrib/pkg/stanza/operator?

We want to use our own copies of stanza operators to allow us to modify their code - the relevant stanza operators have been copied over to processor/signozlogspipelineprocessor/stanza/operator/operators
To make the logspipeline processor use these copies instead of the ones in stanza, we also need to maintain our own registry of these copied operators that get used when unmarshalling the config
Other than the copies of operators at signozlogspipelineprocessor/stanza/operator/operators, our own operator registry signozlogspipelineprocessor/stanza/operator/registry.go and our own operator config that uses that registry instead of the opentelemetry-collector-contrib one signozlogspipelineprocessor/stanza/operator/config.go are the only changes included in signozlogspipelineprocessor/stanza/operator