Renaming of active MCP Start Event

This issue to discuss / track the need for resolving the comment below from https://github.com/finos/fluxnova-plugins/pull/4.

```
A slightly unusual thing I noticed with this implementation is that if you change an MCP tool's name
and deploy the new BPMN it will create a new MCP tool with the new name but the old MCP tool will
remain registered (until the server is restarted). The old tool will start an instance of the new process
definition which is deployed.

Wondering if this might be a cause of concern as if you updated your BPMN, the MCP tool name and
description all at the same time, it would leave an old MCP tool (with an outdated name and description)
which points at the new BPMN. Maybe there is a better way to ensure each MCP tools points to the correct
process definition?
```

Start with the implementation discussed in pull request #4 and trace how MCP tools are registered when a new BPMN process definition is deployed. Determine how renamed tools should relate to their previous registrations, then verify that outdated names and descriptions no longer point to the newly deployed process definition.

Written by the indexing model from the issue text.