[BUG] Passing wrong parameter when calling newConfigurationException method in DotExpanderProcessor

[gaobinlong]

Describe the bug
The first parameter of the method ConfigurationUtils.newConfigurationException() is processorType, but DotExpanderProcessor passes wrong parameter when calling it, even though it doesn't affect the response of the API.

To Reproduce
Steps to reproduce the behavior:

1. Create a ingest pipeline with dot_expander processor, and the value of field doesn't contain a dot:

PUT _ingest/pipeline/test2
{
  "processors": [
      {
        "dot_expander": {
          "field": "foobar"
        }
      }
    ]
}

The response has correct processor type:

{
  "error": {
    "root_cause": [
      {
        "type": "parse_exception",
        "reason": "[field] field does not contain a dot",
        "processor_type": "dot_expander",
        "property_name": "field"
      }
    ],
    "type": "parse_exception",
    "reason": "[field] field does not contain a dot",
    "processor_type": "dot_expander",
    "property_name": "field"
  },
  "status": 400
}

Expected behavior
Correct the first parameter when calling newConfigurationException method in DotExpanderProcessor

Host/Environment (please complete the following information):

• OS: [macOS]
• Version [2.9]

[gaobinlong]

Fixed by #10737.