[BUG] Pipelines: Renaming a toolkit leaves stale references in nodes and YAML

[epamLDadayan]

Title: Pipelines: Renaming a toolkit leaves stale references in nodes and YAML

Description:
After renaming a toolkit, pipelines that reference it keep the old name/ID in node settings and YAML, leaving a stale reference that breaks execution.

Steps to reproduce:

1. Create a toolkit (e.g., GitHub) and add it to an LLM node in a pipeline. Save the pipeline.
2. Rename the toolkit (change its title/ID) and save the toolkit.
3. Reopen the pipeline and inspect the node and YAML.

Actual Result:

• The node still shows the old toolkit name.
• YAML retains the old toolkit reference.
• Pipeline becomes invalid or fails at run time until manually fixed.

Expected Result:

• All node settings and YAML are updated to the new toolkit name/ID immediately after the rename.
• Pipeline remains valid and runs without manual changes.

Notes (optional):
Workaround: manually remove the stale toolkit reference in YAML and reattach the renamed toolkit.

Pipeline for test: https://dev.elitea.ai/alita_ui/406/pipelines/all/12?destTab=configuration&name=BUG+-+2135&viewMode=owner

[epamLDadayan]

@HawkQing1 Pipeline for test: https://dev.elitea.ai/alita_ui/406/pipelines/all/12?destTab=configuration&name=BUG+-+2135&viewMode=owner

[HawkQing1]

@epamLDadayan, @daniilmotsniy and @MikalaiB, from FE perspective, we have no way to correct the toolkit name for nodes in the pipeline, because there is only the stable toolkit name in instructions and FE has no way to figure out the stable toolkit name should be mapped to which new toolkit. It should be fixed from BE side, when the toolkit name is changed, BE should update the related pipeline instructions.

[epamLDadayan]

Verified in DEV env