fix: address transformprocessor config deprecation of 0.119.0

[emiliaFer]

addressing these logs in CI | Nightly Tests

[email protected]/parser_collection.go:364	
one or more statements were modified to include their paths context, please rewrite them accordingly	
{
  "kind": "processor", 
    "name": "transform/truncate", 
      "pipeline": "logs", 
      "statements": {"[0]": {
        "original": "truncate_all(attributes, 4095)", 
        "modified": "truncate_all(log.attributes, 4095)"
      }
    }
}

[github-actions]

PR title 'modify transform processor config to comply with 0.199.0 version bump' does not adhere to conventional commits. Change PR title to ensure that the suggested squash commit follows the conventions and thus ends up in the changelog.

[kb-newrelic]

Fix LGTM but we should include a test to prevent regression and ensure that it actually works. One way to do that would be to leverage the local e2e tests and add a condition that this log entry is no longer present. It's then trivial to verify that this fix works by running the test without your config fix (expecting test to fail) and with the fix (expecting test to pass).

The log should be queryable with something like FROM Log select count(*) where message = 'one or more paths were modified to include their context prefix, please rewrite them accordingly' but make sure to verify that yourself. Over time we'll want to transform that condition into something more general but that can happen in NR-389681

The merge-base changed after approval.

The merge-base changed after approval.