Address issues with source with component names and replacing listeners

[adrianeboyd]

Description

When sourcing a component, the object from the original pipeline is added to the new pipeline as the same object. This creates a situation where there are several attributes that cannot be in sync between the original pipeline and the new pipeline at the same time for this one object:

• component.name
• component.listener_map / component.listening_components for tok2vec and transformer

When running replace_listeners on a component, the config is not updated correctly if the state of the component is incorrect for the current pipeline (in particular changes that should be applied from model.attrs["replace_listener_cfg"] as used in spacy-transformers) due to the fact that:

• find_listeners relies on component.name to set the name in the listener_map
• replace_listeners relies on listener_map to determine how to modify the configs

In addition, there are several places where pipeline components are modified and the listener map and/or internal component names aren't currently updated.

In cases where there is a component shared by two pipelines that cannot be in sync, this PR chooses to prioritize the most recently modified or initialized pipeline. There is no actual solution with the current source behavior that will make both pipelines usable, so the current pipeline is updated whenever components are added/renamed/removed or the pipeline is initialized for training.

Types of change

Bug fix.

Checklist

• I confirm that I have the right to submit this contribution under the project's MIT license.
• I ran the tests, and all new and existing tests passed.
• My changes don't require a change to the documentation, or if they do, I've added all required information.

[adrianeboyd]

I'll let the tests run in the CI first to show the issues. The new tests have a few temporary modifications (marked with TODOs for later removal) so that the test failures show the interesting failures rather than more minor technical issues.

[adrianeboyd]

With the pipeline state kept in sync for the new pipeline by add_pipe, the code block at the end of Language.from_config to sync listener status should no longer be needed.

It doesn't cause any problems, but it should never apply. In particular, it was it looks like it was unintentional that replace_listeners was being checked in two different places and I suspect that at least that part probably should have been removed in #7620.

[adrianeboyd]

Tests for spacy-transformers using replace_listener_cfg: explosion/spacy-transformers#381

• fail with current master: https://github.com/explosion/spacy-transformers/actions/runs/5221455649/jobs/9425733452?pr=381#step:13:210
• succeed with this PR: https://buildkite.com/explosion-ai/spacy-transformers-gpu-test-suite/builds/26