Dispose type module change monitor on failed executor creation

[tobias-tengler]

Fixes #9901

[Copilot]

Pull request overview

This PR addresses Hot Chocolate issue #9901 where failed executor rebuilds could leak TypeModule.TypesChanged subscriptions, leading to exponentially increasing TypeModule.CreateTypesAsync() invocations after repeated OnTypesChanged() signals. The core fix ensures the type module change monitor is disposed when executor creation fails, and adds a regression test to detect subscription leaks when a type instance is registered.

Changes:

• Dispose TypeModuleChangeMonitor (and schema service provider) when request executor creation fails, preventing leaked event subscriptions.
• Add a regression test covering repeated OnTypesChanged() triggers with a registered type instance to ensure CreateTypesAsync() calls don’t grow exponentially.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
src/HotChocolate/Core/src/Types/Execution/RequestExecutorManager.cs	Wrap executor creation in try/catch and dispose the change monitor (and schema services) on failure to prevent leaked TypesChanged subscriptions.
src/HotChocolate/Core/test/Execution.Tests/RequestExecutorManagerTests.cs	Adds a regression test that triggers OnTypesChanged() repeatedly and asserts CreateTypesAsync() calls don’t grow beyond the number of triggers.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.