Raise error on wrong parameter mapping during pipeline definition

[stellasia]

Description

This PR improves the pipeline definition check by raising an error before the pipeline run starts if:

• the same parameter is mapped twice: for instance:

pipe.connect("a", "b", {"value": "a.value"})
pipe.connect("c", "b", {"value": "c.value"})

"value" for component "b" can only be mapped to "a" or "b", not both.

• A parameter is defined in the mapping but not expected by component, for instance:

class MyComponent(Component):
    def run(self, number: int) -> Result:
        pass

pipe.connect("something", "my_component", {"a": "something"})

"a" is not an valid input for "MyComponent".

In both cases, PipelineDefinitionError is raised.

Also, introduce an invalidate method, so that the instance attributes are cleaned properly when invalidating the pipeline (if not, when adding a component after the pipeline has already been validated, the validation would fail because the parameter already exists in the param mapping dict from the previous validation).

Type of Change

• New feature
• Bug fix
• Breaking change
• Documentation update
• Project configuration change

Complexity

Complexity: Low

How Has This Been Tested?

• Unit tests
• E2E tests
• Manual tests

Checklist

The following requirements should have been met (depending on the changes in the branch):

• Documentation has been updated
• Unit tests have been updated
• E2E tests have been updated
• Examples have been updated
• New files have copyright header
• CLA (https://neo4j.com/developer/cla/) has been signed
• CHANGELOG.md updated if appropriate