fix: rename misleading command test names

Renamed to accurately reflect what they verify:
- Forwards_Commands_In_Session_Create -> Session_With_Commands_Creates_Successfully
- Forwards_Commands_In_Session_Resume -> Session_With_Commands_Resumes_Successfully

Actual forwarding verification is in the multi-client test
Client_Receives_Commands_Changed_When_Another_Client_Joins_With_Commands
which proves the server received the commands by checking the
commands.changed event on another client.

Author: MRayermannMSFT

dotnet/test/CommandsTests.cs

@@ -12,7 +12,7 @@ public class CommandsTests(E2ETestFixture fixture, ITestOutputHelper output)
     : E2ETestBase(fixture, "commands", output)
 {
     [Fact]
-    public async Task Forwards_Commands_In_Session_Create()
+    public async Task Session_With_Commands_Creates_Successfully()
     {
         var session = await CreateSessionAsync(new SessionConfig
         {
@@ -31,7 +31,7 @@ public async Task Forwards_Commands_In_Session_Create()
     }
 
     [Fact]
-    public async Task Forwards_Commands_In_Session_Resume()
+    public async Task Session_With_Commands_Resumes_Successfully()
     {
         var session1 = await CreateSessionAsync();
         var sessionId = session1.SessionId;