Fix resource leak in AppComponentTest by disposing service scope

[Copilot]

The AppComponentTest base class creates an IServiceScope but never disposes it, causing resource leaks in the test suite.

Changes:

• Added Scope?.Dispose() in the Dispose() method to properly clean up service scopes
• Used null-conditional operator to handle potential multiple disposal calls safely

public void Dispose()
{
    OnDispose();
    Scope?.Dispose();  // Added
    GC.SuppressFinalize(this);
}

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Copilot]

Pull request overview

This PR addresses a resource leak in the AppComponentTest base class by adding disposal of the IServiceScope instance that is created but never cleaned up.

• Added Scope?.Dispose() call in the Dispose() method to properly release service scope resources
• Used null-conditional operator for safe disposal handling

---

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

[Copilot]

This change may cause test runner hangs. There's an identical AppComponentTest class in test/modules/servicebus/Elsa.ServiceBus.AzureServiceBus.ComponentTests/Abstractions/AppComponentTest.cs that has a similar Scope property, but the disposal is commented out with an explicit warning: "Disposing the Scope here and in other places where it is created somehow seems to cause the test runner to hang when running other test projects."

Before merging this change, please verify that disposing the Scope in this test class doesn't cause similar hanging issues. Consider running the full test suite, including other test projects, to ensure this doesn't introduce instability.

Suggested change

	Scope?.Dispose();
	// Do not dispose Scope here. Disposing the Scope in similar component test base classes
	// has been observed to cause the test runner to hang when running other test projects.